closed from SPLAT-1367

Epic Goal

• Create/reuse infrastructure provisioning steps to use UPI-provisioning method to test the Oracle Cloud Infrastructure (OCI) with platform type External on OpenShift CI, consuming the native e2e workflows, and post-analyzing tooling (junit processors, collectors).

Epic Non-goal

• Create workflows using Assisted Installer
• Create E2E workflows to new provider or not-supported by the CI infrastructure
• Expand research to new Cloud Providers
• Write new e2e tests

Why is this important?

• 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

Scenarios

1. ...

Acceptance Criteria

• 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)
•  
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• 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>
•