Additional VM/CT OVS networking options

[t00l1024]

I'm looking for alternatives or a long term solution to this problem. I'm currently running PVE 5.4-6.

Currently, I can create a network of type OVS Bridge and pass OVS Options via the GUI, which are then reflected in /etc/network/interfaces/ The same is true for the OVS Port - there's a GUI option to set OVS Options for the port.

Two examples would be when setting up the OVS bridge, an configuring it for an external controller or DPDK. ("set Bridge ${IFACE} other-config:datapath-id=0000000000000001-- set-controller ${IFACE} tcp:192.168.1.179:6653 tcp:192.168.1.179:6654)
Easily done.

However, there *isn't* an option to pass similar port options for a container or virtual machine. I'd like to have a "Networking Options" field for a VM/CT that gets passed off to the API or command line, similar to the host networking configuration. I thought about using the LXC lxc.network.script.up parameter, which I suppose would work. But what about a virtual machine? KVM has a 'script' and 'downscript' option, but I need to know the interface name created for the VM (wanting to run '
-- set interface veth-host1 ofport_request=1' when the interface is added to the OVS bridge).

Thanks.

 

[wolfgang]

Hi,

please open a feature request on
bugzilla.proxmox.com

 

[t00l1024]

Hi,

please open a feature request on
bugzilla.proxmox.com

https://bugzilla.proxmox.com/show_bug.cgi?id=2233

Thank you. I hope I've described this feature request adequately.

When I looked into attempting to add this myself to my local installation, I found myself a bit in over my head. It's way more than just adding a GUI field, but how the additional options are stored, extracted and passed to OVS. There's already options and a structure for storing and parsing Debian /etc/network/interfaces, but LXC and Qemu use external scripts.