Uploaded image for project: 'Multiple Architecture Enablement'
  1. Multiple Architecture Enablement
  2. MULTIARCH-2523

Bring release to parity with x86 (4.12 goals)

XMLWordPrintable

    • Bring release to parity with x86 (4.12 goals)
    • False
    • None
    • False
    • Green
    • NEW
    • Done
    • OCPPLAN-8327 - OpenShift support for IBM Power and IBM Z
    • Impediment
    • ppc64le, s390x
    • OCPPLAN-8327OpenShift support for IBM Power and IBM Z
    • NEW
    • 0% To Do, 0% In Progress, 100% Done
    • Hide

      I believe this is fully completed. There is one docs ticket left, but I'm pretty but it appears to be a JIRA hygiene issue.

      Show
      I believe this is fully completed. There is one docs ticket left, but I'm pretty but it appears to be a JIRA hygiene issue.

      Epic Goal

      • Assess P/Z OpenShift gaps and plan to bring in any minor features that are currently missing
      • This is an ongoing effort, similar to addressing technical debt, so will most likely appear in multiple releases

      List of Parity Efforts:

      • <to be filled in>

      Why is this important?

      • While OpenShift on P/Z is pretty complete as far as feature parity and meets all the current customer requirements there are some smaller missing pieces, we need to bring these into the OpenShift on P/Z ecosystem

      Scenarios
      1. After initial assessment should fill in which features we will address in this specific release here

      Acceptance Criteria

      • (Enter a list of Acceptance Criteria unique to the Epic)

      Dependencies (internal and external)
      1. …

      Previous Work (Optional):
      1. …

      Open questions::
      1. …

      Done Checklist

      • CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
      • Release Enablement: <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
      • QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
      • QE - Automated tests merged: <link or reference to automated tests>
      • QE - QE to verify documentation when testing
      • DOC - Downstream documentation merged: <link to meaningful PR>
      • All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.

              jpoulin Jeremy Poulin
              rhn-support-dhardie Duncan Hardie
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: