Epic Goal

• Have end to end continuous integration testing of the agent based ephemeral installation

Why is this important?

• We need to set up reusable infrastructure for running the jobs to enable the CI work for the other epics

Scenarios

1. CI infrastructure that uses virtual machines as target machines
2. CI infrastructure that uses vSphere virtual machines as target machines
3. CI infrastructure that uses bare maetal machines as target machines

Minimal flow

1. Use ci build of openshift-installer instead of fetching as dev-scripts does,
2. dev-scripts image
3. run our dev-scripts make target
4. use openshift-installer agent wait-for completion (in the meantime, Use ZTP code to check the cluster deployment completed)

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

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>