Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-439

[Tech Preview] Support of configure-ovs Alternative

XMLWordPrintable

    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • 0% To Do, 0% In Progress, 100% Done
    • XL
    • 0
    • Program Call
    • this is important. customers want the ability to managed the primary interface with NMState

      In https://issues.redhat.com/browse/OPNET-10 we did some initial investigation of a new design for handling creation of br-ex for OVNK. We successfully came up with a high-level design, but we still need to translate that into an implementable OpenShift feature. The goal for this epic would be to come up with an accepted enhancement. The implementation of the design would likely need to happen in the next release.

      Notable obstacles to this work are:

      • The inability to do per-node configuration in existing OpenShift operators. In order to support things like static IPs we need a way to provide a separate configuration for each node.
      • API team's objections to having NMState configurations represented in the OpenShift API. When we discussed this with them recently they were strongly opposed to NMState as an interface, including the existing baremetal and kubernetes-nmstate cases.

              ddharwar@redhat.com Deepthi Dharwar
              bnemec@redhat.com Benjamin Nemec
              Mike Fiedler Mike Fiedler
              Ashley Hardin Ashley Hardin
              Ben Bennett Ben Bennett
              Chris Fields Chris Fields
              Votes:
              2 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: