OCP/Telco Definition of Done
Epic Template descriptions and documentation.

Support user input consisting of just InstallConfig and AgentConfig

Epic Goal

• Allow users to generate an ephemeral agent based installation ISO from just installConfig and AgentConfig

Why is this important?

• While Zero Touch Provisioning Input is very amenable to automation, it is a more complex input for the user manually setting up a cluster.
• InstallConfig is the canonical start point for OpenShift Installer installation
• Some settings in ZTP are only available in BMH. InstallConfig and AgentConfig will allow customers that do not (or can't) use BMH/BMO to set the same things in their clusters

Scenarios

1. User writes InstallConfig with the general cluster config, AgentConfig with host specific config, then runs openshift-install agent create cluster-manifests, then openshift-install agent create image. After that, boots the target systems with the ISO and gets a successful first OCP cluster

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. Does openshift-install create cluster-manifests need to run explicitly?

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>