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

ovn-operator should create two config maps for edpm deployment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • rhos-18.0.4
    • None
    • ovn-operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • ?
    • ?
    • None
    • Moderate

      Currently the edpm deployment needs two variables from the Control Plane, this two variables are stored and shared using the `ovncontroller-config` config Map. This CM contains the following info:

      • OVNEncapType
      • ovn_remote

      And this is created by the ovncontroller_controller.

      This worked fine until OSPRH-7463 [0] was merged, which modified  openstack-operator to not create OVNController CR when nicMappings was not configured (hence not creating the OVNController CR and not triggering reconcile on ovncontroller_controller). Then since ovncontroller was not reconciled, this Config Map needed by the edpm deployment was not created.

      A fix was provided by OSPRH-10372 [1] but the info provided to the EDPM should be done in two config maps:

      • the first map, created by ovnController should contain the OVNEncapType info (As this information is stored on OVNController.Spec.ExternalIDs)
      • the second map, created by ovnDBCluster-sb should contain the ovn_remote, as it's stored on ovndbcluster.Status.DBAddress

      This will entail changes on how the edpm gets deployed, as currently it only expects a single config map called ovncontroller-config.

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

                Created:
                Updated: