Epic Goal

• Identify current state of ARM ecosystem support in OpenShift
• Define next steps for design and implementation

Why is this important?

ARM is the next leg of the OpenShift journey. In order to tackle ARM enablement with an effective strategy, the current state of the relevant components in the ecosystem has to be identified first.

The goal is for all stakeholders across involved teams and pillars to be aware of the effort, to be involved in the planning, and to come to an agreement with regards to the next steps.

Acceptance Criteria

• State of ecosystem is well-known and documented
  • State of HW/Firmware/SW support for supportable boards (targets: AWS Graviton2 first, BareMetal second)
  • State of ARM OS image composes with COSA
  • State of ARM container builds with ART/Prow
• The next steps have been identified and clearly articulated in a written doc
• The next steps have been converted into Jira cards and planned for in Sprint

Dependencies (internal and external)

1. CoreOS Team
2. Multi-Arch Team
3. ART and CPaaS Teams
4. ...

Previous Work:

1. https://projects.engineering.redhat.com/browse/PLTSOCP-2166
2. https://projects.engineering.redhat.com/browse/PLTSOCP-2
3. https://issues.redhat.com/browse/GRPA-2475
4. https://docs.google.com/document/d/1yLApRT2yysaq3fD1z_DGVSDqC5WZWwboyYmgKT5rssE
5. https://docs.google.com/document/d/1dJEt866zxD-ieb1qlutNANqfzJ0lgg8k0vws7TtB0_o

Open questions:

1. ...

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>