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

Support IPI PowerVC in openshift-installer [FeatureGate: Tech Preview]

XMLWordPrintable

    • IPI on PowerVC
    • None
    • 0% To Do, 100% In Progress, 0% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • Hide

      [20 Nov] <Green> Green
      * PR Merged https://github.com/openshift/installer/pull/9806
      ** Patrick (Installer Lead) approved
      ** Martin (OpenStack) LGTM

      Thank you for the assistance.

       

      [13 Nov] <RED
      > Yellow

       

      Show
      [20 Nov] < Green > Green * PR Merged https://github.com/openshift/installer/pull/9806 ** Patrick (Installer Lead) approved ** Martin (OpenStack) LGTM Thank you for the assistance.   [13 Nov] < RED > Yellow Mark has PRs ready, and needs attention of the Reviewers to get it merged. Needs attention - Main https://github.com/openshift/installer/pull/9806 Started to get attention, slow progress - Patrick submitted his review Merged - OpenStack bug fix https://github.com/openshift/installer/pull/10057  
    • L

      Epic Goal

      Implement a method of installing OpenShift on PowerVC through the OpenShift Installer.

      The code reuses the OpenStack provider (PowerVC's code is OpenStack). The code, where there are differences for PowerVC, is modularized.

      Ensure any code added to the openstack provider does not interfere with existing deployment methods.

      Why is this important?

      • Provides an easy way to bring a cluster up on premise. PowerVC provides a backend that makes it easy to provision Power virtual machines and the OpenShift installer provides an easy way to deploy OpenShift.

      Scenarios

      1. A cluster-admin, deploy a cluster on PowerVC using IPI
      2. A cluster-admin, destroys a cluster on PowerVC using IPI.
      3. A cluster-admin scales a MachineSet with PowerVC

      Acceptance Criteria

      • The code is behind a featuregate
      • A user can install an OpenShift Cluster on PowerVC using IPI PowerVC.
      • The user sets up minimum resources to support the PowerVC use-case.

      Dependencies (internal and external)
      1. API team
      2. Installer Team
      3. ShiftOnStack
      3.CLOUD
      3.Ingress
      3.Storage

      UPI install with PowerVC already has an image.
      Previous Work (Optional)
      A spike in 4.19 capture the development https://issues.redhat.com/browse/MULTIARCH-4980

      Open questions

      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'.

          There are no Sub-Tasks for this issue.

              mturek.coreos Michael Turek
              mturek.coreos Michael Turek
              Brian Cogan
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: