XML

Word

Printable

Epic Name:
[platform-external][CI] Increase test scope for Platform External (core)
Story Points:
24
Blocked:
False
Blocked Reason:
None
Ready:
False
Color Status:
Not Selected
Epic Status:
To Do
Feature Link:
OCPSTRAT-1136 - Onboarding New Providers/Platforms (Phase 4)
Parent Link:
OCPSTRAT-1136Onboarding New Providers/Platforms (Phase 4)
Hierarchy Progress:
50
Hierarchy Progress Bar:

50% 50%
Status Summary:

Hide

C/I/T: 5/19/24

Show
C/I/T: 5/19/24

Epic Goal

Create E2E workflow (core/default) to validate the OpenShift installation with platform external in well-known cloud provider (AWS).
Create native support in the regular/default e2e CI workflow to create platform External installation type
Create/reuse infrastructure provisioning steps to use UPI-provisioning flow to test a well-known cloud provider (AWS), supported by CI, with platform external on OpenShift CI, consuming the native e2e workflows, and post-analyzing tooling (sippy, junit processors, collectors).
Implement the E2E described in the documentation shared to the partners: https://docs.providers.openshift.org/platform-external/installing/

Epic Non-goal

Platform External is a native OCP feature introduced in 4.13. Clusters installed with Platform External type does not have installation automation, requiring to run UPI-style to provisione infrastructure resources required to install OpenShift. Currently there is no workflow supporting the default E2E CI Step[1], only OPCT workflow[2]. The E2E workflow has a lot of integrations with OpenShift CI ecosystem, including results processing, external tooling like Sippy providing feedback and so on.
The default tooling we are advising partners to self-running, and self-evaluting, is OPCT[3]. The tool aims to provide quick access and post-processing results outside OpenShift CI infra to our partners. Having native E2E workflow and OPCT workflow running side-by-side in OpenShift CI infrastructure, would help to;
- Unblock OCP Engineers to implement custom e2e test using native conformance workflow and test in OpenShift CI using well-known provider (AWS)
- Feed OPCT with native E2E conformance tests executed by CI, allowing to compare/benchmark the tool to improve the quality of the results from OPCT, and decrease the risks of the tool-specific issues.
- Unblock OCP engineers to implement workflows using OPCT, same used by the partners, decreasing the gap in the knowledge and requirement to run manually the tool

CI - MUST be running with the default E2E openshift/conformance/parallel suite in clusters installed on AWS using platform type External
CI - MUST be running with the default E2E openshift/conformance/parallel suite in clusters installed on AWS using platform type External and CCM installed on Day-0/1 (as described in the documentation)
CI - MUST be running with the OPCT default workflow in clusters installed on AWS using platform type External
CI - MUST be running with the OPCT default workflow in clusters installed on AWS using platform type External and CCM installed on Day-0/1 (as described in the documentation)
...

CI - CI is running, tests are automated and merged.
DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
DEV - Downstream build attached to advisory: <link to errata>