Eric Pouyoul
Eric Pouyoul
Not certain if this issue is happening or not.
The proposed fix is to implement the VPN Service JAVA API (enos #23 ). This will create effectively a java singleton wrapping up the python instance running the MP-VPN. This...
Commit of the branch lomax-enos-113 fixes this problem
When trying to create a container on the production ProxMox cluster, the command fail with "missing request module". I am not sure if that is due to a bug in...
Auth seems to be restricted to the es.net realm. The proxmox enos user is within the proxmox realm.
proposal https://docs.google.com/a/lbl.gov/document/d/1slQhqlIa51Kon1St6Y1Zokr2YkdSWu38maSdq9l42qk/edit?usp=sharing
A simpler design based on one to many rabbitmq is going to be first deployed. Therefore this issue is no longer for the release 1.1 milestone
The problem was that the VPN is implementing a vpn cache for optimizing DB access which conflicts with the Container cache which was introduced later.
Verified that properties are now properly in the database, but they seem to be stored as object and not json.
Current status: most of the objects are created when mpvpn service starts but the various flow entries are not properly stored / reloaded.