Goal

• We want to move our current Metal Single Node lanes over to AWS and using RHEL based images, to take advantage using CPUs similar to telco customers and a cost reduction over the existing provider Equinix.

Why is this important?

• We need to be able to test our SNO deployments with as close of a configuration as our customers, and do this in a reasonable way.
• We recently did a spike into the different offerings for metal and AWS provided the best option for CPU offerings and price. See: OCPEDGE-992
• Our current Metal lanes use Equinix and RockyOS for running tests, this has not been a problem recently but by moving over to AWS we would get a cheaper metal instance that is closer to our telco customers as well as an easier job of using RHEL as our base OS (Equinix has surcharge for RHEL or you can bring your own but that seems to include extra complexity)
  • See Step: https://steps.ci.openshift.org/workflow/baremetalds-sno
• If we don't do this, then the current lanes just stay as is, they really shouldn't break the only thing that might change in the future is the use of RockyOS but otherwise these lanes currently are not CPU dependent like some other lanes we might decide to do.

Scenarios

1. As a developer I expect the existing metal CI should continue to function as if nothing changed.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Existing https://github.com/openshift/assisted-test-infra should be able to run on RHEL in AWS as it does on RockyOS in Equinix.

Dependencies (internal and external)

1. Internal dependency on https://github.com/openshift/assisted-test-infra

Previous Work (Optional):

1. Research on metal platform offerings OCPEDGE-992

Open questions:

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Technical 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>