Uploaded image for project: 'Agent-based Installer for OpenShift'
  1. Agent-based Installer for OpenShift
  2. AGENT-994

E2E validation of OpenShift on OCI with Bare Metal

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • None
    • E2E validation of OpenShift on OCI with Bare Metal
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-1203 - [GA] OpenShift on Oracle Cloud Infrastructure (OCI) Bare metal
    • OCPSTRAT-1203[GA] OpenShift on Oracle Cloud Infrastructure (OCI) Bare metal
    • 33% To Do, 0% In Progress, 67% Done

      Epic Goal

      • Validate E2E that Openshift can be deployed in Oracle Cloud Infrastructure using Bare Metal Machines
      • This should be a QE-only job as no code changes should be required in ABI
      • The E2E test will also provide feedback on the existing integration between OCP and OCI so we can use this information to update documentation and share input with the engineering teams. As an example, this exercise was done recently for the Assisted Installer E2E workflow --> https://docs.google.com/document/d/1Q6cl4yWhRV-h6P6Jqq2IIm-VjrJjbm9ImfkjVuaDG9U/edit

      Why is this important?

      • Before we can declare GA support for OCP on OCI with BM we need to validate that the installation tools we use for this platform work with the existing artifacts from Oracle

      Scenarios

      1. Deploy OpenShift on Oracle Cloud Infrastructure using VMs for the Control Plane Nodes and Bare Metal Nodes for the Compute Nodes
      2. Deploy OpenShift on Oracle Cloud Infrastructure using Bare Metal Nodes for the Control Plane and Compute Nodes

      Acceptance Criteria

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

      Previous Work:

      1. ABI is already supported to deploy OpenShift on OCI with VMs

      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>

              rhn-support-pamoedom Pedro Jose Amoedo Martinez
              mak.redhat.com Marcos Entenza Garcia
              Manoj Hans Manoj Hans
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: