Detect OVN native services enabled with neutron services

Bug #1628567 reported by Richard Theis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-ovn
Opinion
Medium
Unassigned

Bug Description

The OVN native L3 service must not be enabled with the conventional neutron L3 service. The same is true for the OVN native DHCP service and eventually will be true for the OVN native metadata service (https://review.openstack.org/#/c/315305/). Detecting these situations is currently done via DevStack deployments. However, it should also be done during runtime to help other deployment technologies.

Richard Theis (rtheis)
Changed in networking-ovn:
status: New → Confirmed
Changed in networking-ovn:
importance: Undecided → Medium
Revision history for this message
Lucas Alvares Gomes (lucasagomes) wrote :

I think that would be outside of networking-ovn's scope. I'm trying to think how we could do it. We could fail at start time if the Neutron L3 plugin is listed in the neutron.conf ? Even then, it doesn't seem to be up to a plugin to check for such things.

There are many permutations that can be done with these services/agents. For example, people may rely on the Neutron DHCP agent for things like SRIOV or PXE booting (which are currently not supported by the native DHCP in OVN) even tho OVN has it's own native DHCP service.

I still think that the deployment tool is the right place to check for these problems.

Changed in networking-ovn:
status: Confirmed → Opinion
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.