Support DNS for ovn_{nb,sb}_connection
Bug #2028442 reported by
Mohammed Naser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
High
|
Unassigned |
Bug Description
At the moment, it seems that when using a DNS hostname for `ovn_nb_connection` or `ovn_sb_
It seems that the `ovs` library does not resolve an IP address before proceeding, I'm not sure if we should be resolving things and passing them on resolved to OVS, or tryign to look for fix upstream.
This is pretty critical for HA deployments that rely on multiple replicas with hostnames (i.e. a Kubernetes StatefulSet)
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → High |
To post a comment you must log in.
@mnaser, it's recently implemented in OVS[1] by Terry, can you check/confirm if that's what works for your case.
[1] https:/ /github. com/openvswitch /ovs/commit/ 4d55a364ff60d89 4dce4e2e97a489d 81520dc663