XML

Word

Printable

Epic Name:
[OCI] Execute the one-off e2e validation of Assisted Installer installation
Work Type:
BU Product Work
Story Points:
11
Blocked:
False
Blocked Reason:
None
Ready:
False
Color Status:
Not Selected
Epic Status:
To Do
Feature Link:
OCPSTRAT-1203 - [GA] OpenShift on Oracle Cloud Infrastructure (OCI) Bare metal
Parent Link:
OCPSTRAT-1203[GA] OpenShift on Oracle Cloud Infrastructure (OCI) Bare metal
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done

Epic Goal

Validate the Assisted Installer documentation to deploy OpenShift on Oracle Cloud (OCI) VMs and BMs, targetting mixed environments in a single workflow.
Feed Documentation team targeting the 4.17 release
Collect action items to review the CI jobs using OCI automation (terraform)

References:

The scope of validation (e2e test case): manually deploy OCP on OCI with platform type External using Assisted Installer SaaS
The mixed topology to test: Control Plane in VMs, Worker nodes using Bare Metal instances
The documentation references to review, Oracle and RH:
- Red Hat: https://docs.openshift.com/container-platform/4.16/installing/installing_oci/installing-oci-assisted-installer.html
- Oracle: https://docs.oracle.com/pt-br/iaas/Content/openshift-on-oci/overview.htm
- Oracle deployment config version (beta-v1): https://github.com/oracle-quickstart/oci-openshift/tree/beta-v1
The feedback channel to feed the Documentation team: Google docs will be created, or a fork of openshift-docs - depending of the amount of suggestions - which one that would be more collaborative
The feedback channel to feed the Oracle team while reviewing the Terraform code: Joint Slack channel ext-redhat-oracle-offerings
Release to be used: Latest 4.17 available in AI: 4.17-rc.1

Why is this important?

manually deploy OCP on OCI with platform type External using Assisted Installer SaaS

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

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>