Detect OVN native services enabled with neutron services
Bug #1628567 reported by
Richard Theis
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:/
Changed in networking-ovn: | |
status: | New → Confirmed |
Changed in networking-ovn: | |
importance: | Undecided → Medium |
To post a comment you must log in.
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.