-
Story
-
Resolution: Unresolved
-
Major
-
None
-
Proactive Architecture
-
8
-
False
-
None
-
False
-
-
-
8
USER STORY:
- As a OCP Engineer, I would like to install OCP clusters using platform type External using ARM64 architecture, then run OPCT conformance workflow, so I can make confidence that new platform type is exercised/tested with arm64 getting confidence to recommend to partners.
- As a engineer working in OPCT project I would like to have e2e artifacts from executions on platform type External in ARM64 clusters to I can have confidence the e2e payload is working correctly in that provider/platform.
- As a Partner I would like to install OCP cluster on myCloud using platform type External with ARM64, so I can start offering that installation method to my customers
DESCRIPTION:
We need to make sure multi-arch (x86 and ARM64) installs is exercised on CI using platform type External to have confidence when offering that validation method to partners using that integration method.
The documentations [2] are entrypoint to create multi-arch compute machines.
Currently there are several CI tests exercising ARM64 and multi-arch payloads, this effort must using multi-arch payloads as recommended. See more details in the reference[1].
Currently work/CI jobs exercising single ARM64 and multi-arch payloads:
for ARM (using the arm only release payload):
periodic-ci-openshift-multiarch-master-nightly-4.17-ocp-e2e-aws-ovn-arm64
periodic-ci-openshift-multiarch-master-nightly-4.17-ocp-e2e-upgrade-aws-ovn-arm64
periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.17-periodics-e2e-aws-arm
periodic-ci-openshift-multiarch-master-nightly-4.17-ocp-e2e-ovn-serial-aws-arm64
periodic-ci-openshift-multiarch-master-nightly-4.17-ocp-e2e-aws-ovn-arm64-single-node
periodic-ci-openshift-multiarch-master-nightly-4.17-ocp-e2e-aws-ovn-arm64-techpreview
periodic-ci-openshift-multiarch-master-nightly-4.17-ocp-e2e-aws-ovn-arm64-techpreview-serial
multi, starts as an x86 cluster w/multi-release payload, adds arm nodes after install:
periodic-ci-openshift-multiarch-master-nightly-4.17-ocp-e2e-aws-ovn-heterogeneous periodic-ci-openshift-multiarch-master-nightly-4.17-ocp-e2e-aws-ovn-heterogeneous-upgrade periodic-ci-openshift-multiarch-master-nightly-4.17-upgrade-from-stable-4.16-ocp-e2e-aws-ovn-heterogeneous-upgrade
Required:
- ARM64 periodic jobs, using multi-arch payloads, installing an OpenShift cluster using platform type External using AWS as provider (supported on CI).
- Do we need any documentation update? Need to check:
- Multi-arch for compute machines[2]
- Oracle Cloud installs [3]
- Infrastructure Provider Onboarding Guide
Nice to have:
- Multi-arch periodic jobs installing an OpenShift cluster using platform type External using AWS as provider (supported on CI).
ACCEPTANCE CRITERIA:
- CI PRs merged introducing periodic jobs
- ARM64 Jobs must have similar results as x86 installs (similar install variant)
- Map any further work, specially related to the documentation
ENGINEERING DETAILS:
[1] https://redhat-internal.slack.com/archives/GVB4SH2BU/p1721249411810949
[2] multi-arch entrypoint: https://docs.openshift.com/container-platform/4.16/post_installation_configuration/configuring-multi-arch-compute-machines/multi-architecture-configuration.html
- blocks
-
OPCT-291 [Review][OCI] Review installs with single-arch ARM64 for VM and BM
- New