Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-483

Data Plane Adoption steps: Designate

XMLWordPrintable

    • [RFE][OSP 18.0] Data Plane Adoption: Designate
    • False
    • Hide

      None

      Show
      None
    • False
    • Committed
    • Committed
    • Committed
    • In Progress
    • RHOSSTRAT-290 - Data plane adoption support for Designate in RHOSO
    • QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
    • Committed
    • rhos-connectivity-vans
    • Committed
    • 0% To Do, 50% In Progress, 50% Done
    • 2023Q1, 2023Q3, 2023Q4

      Define the procedure and develop any necessary tooling to adopt a Director-deployed Designate Control Plane service and Unbound servers into a Podified Control Plane.

       

      While there is a "basic" scenario where we simply move all of the zone management into the RHOSO cluster, it is an unlikely path for customers for a few reasons:

      • DNS servers outside of the OpenStack cluster may delegate to the Designate BIND9 servers (i.e. they have zones that refer to those BIND9 servers by IP) and/or may be part of a domain name configuration in DNS registries like godaddy etc. There are downtime considerations.
      • Neutron networks will reference the Unbound servers by IPs which may not portable to the OpenShift cluster.

              rhn-engineering-beagles Brent Eagles
              jira-bugzilla-migration RH Bugzilla Integration
              rhos-dfg-networking-squad-vans
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: