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

oc mirror feature parity for IBM Power and IBM zSystem

    XMLWordPrintable

Details

    • False
    • Hide

      None

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

    Description

      Feature Overview (aka. Goal Summary)  

      You can use the oc-mirror OpenShift CLI (oc) plugin to mirror all required OpenShift Container Platform content and other images to your mirror registry by using a single tool. It provides the following features:

      • Provides a centralized method to mirror OpenShift Container Platform releases, Operators, helm charts, and other images.
      • Maintains update paths for OpenShift Container Platform and Operators.
      • Uses a declarative image set configuration file to include only the OpenShift Container Platform releases, Operators, and images that your cluster needs.
      • Performs incremental mirroring, which reduces the size of future image sets.

      This feature is track bring the oc mirror plugin to IBM Power and IBM zSystem architectures

      Goals (aka. expected user outcomes)

      Bring the oc mirror plugin to IBM Power and IBM zSystem architectures

       

      Requirements (aka. Acceptance Criteria):

      oc mirror plugin on IBM Power and IBM zSystems should behave exactly like it does on x86 platforms.

       

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

       

      Questions to Answer (Optional):

      Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

       

      Out of Scope

      High-level list of items that are out of scope.  Initial completion during Refinement status.

       

      Background

      Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

       

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

       

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

       

      Interoperability Considerations

      Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

      Attachments

        Activity

          People

            rhn-support-dhardie Duncan Hardie
            rhn-support-dhardie Duncan Hardie
            Dylan Orzel Dylan Orzel
            Jeremy Poulin Jeremy Poulin
            Stephanie Stout Stephanie Stout
            Prashanth Sundararaman Prashanth Sundararaman
            Duncan Hardie Duncan Hardie
            Jon Thomas Jon Thomas
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: