-
Story
-
Resolution: Done
-
Critical
-
None
-
None
SB database is managed by OVNDbCluster controller. The latter doesn't define a stable endpoint (IP or DNS) that could be used in EDP configuration, that would work even after ovsdb-server pod restarts with a different IP address.
The idea here would be to extend OVNDbCluster controller to define a Service that could be used in EDP configuration as a hostname in edpm_ovn_dbs. It may also be used in edpm_ovn_metadata_agent_metadata_agent_ovn_ovn_sb_connection once metadata agent support DNS connection strings.
- blocks
-
OSPRH-2191 [Dev] implement TLS for OVN services
-
- Closed
-
- depends on
-
OSPRH-646 Validate that EDP OVN SB clients (metadata agent, ovn-controller) can connect to a db cluster through a single address (IP, DNS)
-
- Closed
-
- is related to
-
OSPRH-662 Support dns domain names in the ovn's connection string configured in Neutron agents config files
-
- Closed
-
- links to
- mentioned on