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

OpenShift Core Networking Improvements SDN

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-16OpenShift - Kubernetes and Core Platform
    • 100
    • 100% 100%
    • 0
    • 0
    • Program Call

      We drive OpenShift cross-market customer success and new customer adoption with constant improvements and feature additions to the existing capabilities of our OpenShift Core Networking (SDN, Network Edge, Network Observability). This feature captures that natural progression of the product for that development that does not align neatly to an existing Jira Feature.

      Goals

      • Feature enhancements (performance, scale, configuration, UX, ...)
      • Modernization (incorporation and productization of new technologies)

      Requirements

      • Core Networking Stability
      • Core Networking Performance and Scale
      • Core Neworking Extensibility (e.g. Multus CNIs)
      • Core Networking UX (Observability)
      • Core Networking Security and Compliance

      In Scope

      • SDN (CNI plugins: openshift-sdn, ovn-kubernetes, network plumbing, network policy, bare metal networking, traffic routing, ...)

      Out of Scope

      There are grey areas, but in general:

      • CNV
      • Service Mesh
      • CNF
      • Telco-specific customer solutions (versus in-product features)

      Documentation Considerations

      Questions to be addressed:

      • What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
      • Does this feature have doc impact?
      • New Content, Updates to existing content, Release Note, or No Doc Impact
      • If unsure and no Technical Writer is available, please contact Content Strategy.
      • What concepts do customers need to understand to be successful in [action]?
      • How do we expect customers will use the feature? For what purpose(s)?
      • What reference material might a customer want/need to complete [action]?
      • Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available.
      • What is the doc impact (New Content, Updates to existing content, or Release Note)?

            ddharwar@redhat.com Deepthi Dharwar
            mcurry@redhat.com Marc Curry
            Chris Fields
            Michael Fiedler Michael Fiedler
            Ashley Hardin Ashley Hardin
            Chris Fields Chris Fields
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: