Uploaded image for project: 'OpenShift Installer'
  1. OpenShift Installer
  2. CORS-3659

Add GCP C4/C4A Machine Series to tested instances for OCP

XMLWordPrintable

    • Add GCP C4/C4A Machine Series to tested instances for OCP
    • BU Product Work
    • False
    • None
    • False
    • Green
    • In Progress
    • OCPSTRAT-1624 - Enable OpenShift on GCP C4/C4A Machine Series
    • OCPSTRAT-1624Enable OpenShift on GCP C4/C4A Machine Series
    • 10% To Do, 0% In Progress, 90% Done
    • Hide

      Green - 

       

      Added validation for C4A instances. These instances are for Arm Architecture, so there were a few extra items to check for validation. Waiting on The ability to create these types in the installer GCP project.

       

      The installer GCP project was given the ability to create C4A instances. There are specific zones that can support these instance types. These zones are not currently able to be validated, because GCP does not provide that information through an API. 

      Show
      Green -    Added validation for C4A instances. These instances are for Arm Architecture, so there were a few extra items to check for validation. Waiting on The ability to create these types in the installer GCP project.   The installer GCP project was given the ability to create C4A instances. There are specific zones that can support these instance types. These zones are not currently able to be validated, because GCP does not provide that information through an API. 

      Epic Goal

      Why is this important?

      • This is a new Machine Series Google has introduced that customers will use for their OpenShift deployments

      Scenarios

      1. Deploy an OpenShift Cluster with both the Control Plane and Compute Nodes running on C4 GCP Machines
      2. Deploy an OpenShift Cluster with both the Control Plane and Compute Nodes running on C4A GCP Machines

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.

      Dependencies (internal and external)

      1. Hyperdisk-balanced enablement work via OCPSTRAT-1496

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              rh-ee-bbarbach Brent Barbachem
              mak.redhat.com Marcos Entenza Garcia
              Jianli Wei Jianli Wei
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: