On Fri, 2022-03-04 at 18:33 +0100, Rodolfo Alonso Hernandez wrote:
Hi Arnaud:
Those parameters should be set in nova.conf, in the "os_vif_XXX" section
[1].
"network_device_mtu" is deprecated. The interface MTU is retrieved from the
network MTU. "ovs_vsctl_timeout" is deprecated too, we don't use vsctl
commands anymore.
actully we do use vsctl at least in ci but it is deprecated.
we are currently using it in ci to workaround a bug in the ovs python bindings.
after the RC period is clear i might revert that since i think the ovs python bidnign are
fixed but im not sure they are fixed in ubuntu 20.04 so i dont want to regress the ci stablity
currently by reverting to the native bindings.
https://review.opendev.org/c/openstack/devstack/+/796826
ill update https://github.com/openstack/devstack/blob/master/lib/os-vif#L6 to native
once we are sure https://bugs.launchpad.net/os-vif/+bug/1929446 is fixed in the ovs python bindings.
Maybe Nova folks can extend my answer.
Regards.
[1]
https://github.com/openstack/nova/blob/50fdbc752a9ca9c31488140ef2997ed59d861a41/releasenotes/notes/libvirt-uses-os-vif-plugins-31a0617de0c248b9.yaml
On Fri, Mar 4, 2022 at 6:18 PM Arnaud Morin <arnaud.morin@gmail.com> wrote:
Hey all,
When I take a look at [1], I can see some parameters, such as
network_device_mtu, isolate_vif, etc.
As far as I can tell, nova is using these params when plugging the port
in OVS (if using OVS as ml2 plugin of course).
But I cannot find the config params in the documentation: [2]
Am I missing something?
Cheers,
Arnaud.
[1] https://github.com/openstack/os-vif/blob/master/vif_plug_ovs/ovs.py
[2] https://docs.openstack.org/nova/latest/configuration/config.html