octavia-health-manager requires a host-wise plugged interface to the lb-mgmt-net
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Invalid
|
Medium
|
Unassigned |
Bug Description
Problem
The lb-mgmt-net subnet could collide with any of the host networks, and the use of the dhcp-agent [2] could overwrite host settings at port plug time, I guess that deployments should at least get the fixed IP provided by neutron and stick to that.
Solutions
I believe it should be the health-manager itself who should be plugging the interface, and not the deployment tools. [1]
Ideally, we could plug the interface inside a netns, and have a sub-agent of the health-manager inside the namespace (rootwrap-
[1] https:/
[2] https:/
[3] https:/
tags: | added: rfe |
Changed in octavia: | |
importance: | Undecided → Medium |
The DHCP and L3 agents also need ports in Neutron networks. They do it by having the agent create a namespace and a port in the namespace. We don't do it by requiring the OpenStack deployment tool set up a port in the root namespace. Hopefully the disadvantages of this approach are clear.