-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
the user can configure neutron-dns integration
-
3
-
False
-
False
-
Committed
-
Proposed
-
OSPRH-4410 - Designate support for RHOSO (Target 18.0 FR2)
-
Committed
-
Proposed
-
50% To Do, 0% In Progress, 50% Done
-
-
It must be possible to configure neutron-designate integration, both so designate records are automatically updated and that networks are configured to point to the managed resolver by default.
This has interesting implications as it involves :
- altering the neutron service plugin list to add dns_domain_ports and access information for designate
- configuring the neutron plugin conf with [ovn]dns_servers=[ips of the unbound servers] (only relevant for in cluster bind)
TripleO does this automatically because the information is available at deploy time. It's more complex with the podified control plane because we do not have all of this information at the time neutron is deployed.