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

Don't create ovn-controller POD if there are no NicMappings configured

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • OSPRH-4727 - ovn-operator enhancements (Post OSP18 GA)
    • ?
    • ?
    • 3

      In general ovn-controller POD is deployed on the control plane by the ovn-operator to provide centralized dataplane networking functionalities like e.g. SNAT, port_forwarding, etc. That's why EnableChassisAsGateway is set to True by default in the ovn-controller CRD.

      But (probably) all of those functinalities requires connectivity to the External network so some configuration of the NicMappings is required for that. It can't really be done with any sane defaults as this setting heavily depends on the hardware used by the customer.

      So goal of this story is to:

      1. Investigate if we really need ovn-controller pod to be deployed if it isn't connected to any external network (no NicMappings configured), maybe there is some other function for which it is/can be used with only connectivity to the tenant network,
      2. If this ovn-controller is only really useful when connected to the external network, then update ovn-controller controller so that POD will not be started at all if there is no NicMappings provided.
      3. Deprecate and eventually remove EnableChassisAsGateway option.

            averdagu@redhat.com Arnau Verdaguer Puigdollers
            skaplons@redhat.com Slawomir Kaplonski
            rhos-dfg-networking-squad-neutron
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: