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

Configure more than one ovn-controller in the OpenStackControlPlane CR

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • ovn-operator
    • None
    • Configure more than one ovn-controller in the OpenStackControlPlane CR
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • Proposed
    • Proposed
    • To Do
    • Proposed
    • Proposed
    • Low

      Goal:

      Allow to configure more than one ovn-controller, each belongs to a different AZs to be deployed on the OCP nodes (in the POD).

      Currently ovn-operator's API (CRD) allows to specify `OvnAvailabilityZones` as list of AZs and that list is then set in the `external-ids:availability-zones` for each of the ovn-controller PODs. But in some cases it may be required to deploy ovn-controller on the nodes which belongs to different AZs so something like list of the ovn-controllers should be specified, and each of the elements on that list would have different `nodeSelectors` and `OvnAvailabilityZones` specified.

      Open questions:

      This came up to me during the call about setting deployment for one of the customers but finally that customer will not need this change as they will deploy ovn-controllers in the edpm networker nodes. So the open question is if we will really have customers who would require this change.

              Unassigned Unassigned
              skaplons@redhat.com Slawomir Kaplonski
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: