Uploaded image for project: 'OpenShift Top Level Product Strategy'
  1. OpenShift Top Level Product Strategy
  2. OCPPLAN-8327

OpenShift support for IBM Power and IBM Z

XMLWordPrintable

    • False
    • False
    • ?
    • No
    • ?
    • ?
    • ?
    • 100
    • 100% 100%

      Feature Overview

      • OpenShift now runs as a fully supported platform on IBM Z and IBM Power systems however there are still feature gaps when compared to OpenShift and other areas of opportunity unique to the P/Z platforms. This feature will track the ongoing epics that will be used to bring existing and new core OpenShift features to these systems.

      Goals

      • Relevant existing core features with a valid business case should be made available (eng, QE, docs, SRE) on Power and Z
      • New features that are coming online which have a valid business case to run on Power or Z should be brought across
      • Any specific platform dependent features (such as unique storage) can be tracked here

      Requirements

      • Features do not have to appear on both platforms at the same time, there may be a delay between the same feature appearing on one platform vrs the other, or in some cases the feature will only make sense (business wise or technically wise) to bring to a single specific platform.

       

      Out of Scope

      • "Addons" - the OpenShift Addons will be tracked in another feature

      Background, and strategic fit

      This Section: What does the person writing code, testing, documenting need to know? What context can be provided to frame this feature.

      Assumptions

      • ...

      Customer Considerations

      • ...

      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)?

            Unassigned Unassigned
            rhn-support-dhardie Duncan Hardie
            Jon Thomas Jon Thomas
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: