The neutron team is finally removing the ovs-ofctl option. https://review.openstack.org/#/c/599496/
The ovs-ofctl of_interface option wasn't default since Newton and was deprecated in Pike. So, if you are a long time ovs-agent user and upgrading to a new coming release, you must switch from the ovs-ofctl implementation to the native implementation and are affected by the following issue. https://bugs.launchpad.net/neutron/+bug/1793354 The loss of communication mentioned in this bug report would be a few seconds to a few minutes depending on the number of network interfaces. It happens when an ovs-agent is restarted with the new of_interface (so only once during the upgrade) and persists until the network interfaces are set up. Please speak up if you cannot tolerate this during upgrades. IIUC, this bug is unfixable and I'd like to move forward as maintaining two of_interface implementation is a burden for the neutron team. -- IWAMOTO Toshihiro _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
