XML

Word

Printable

Type: Epic
Resolution: Unresolved
Priority: Blocker
Fix Version/s: openshift-4.20
Affects Version/s: None
Component/s: Installer / Agent based Installer
Labels:
- no_core_payload

Epic Name:
TP-OVE ISO build and release
Blocked:
False
Ready:
False
Color Status:
Yellow
Epic Status:
In Progress
Feature Link:
OCPSTRAT-1985 - [Tech Preview - Ph 1] Agent Installer for OpenShift Virtualization
Parent Link:
OCPSTRAT-1985[Tech Preview - Ph 1] Agent Installer for OpenShift Virtualization
Hierarchy Progress Bar:

10% To Do, 19% In Progress, 71% Done
Size:
L
Status Summary:
Hide

10-15-2025: Yellow

Changed to use a different releease pipeline - rh-advisories, on recommendation from CLOUDDST team to better accommodate the ISO when its pushed to Content Gateway and not expose as separate product. Refining ReleasePlanAdmission with feedback from CLOUDDST. Identified tests which will need to be excluded and added them to EnterpriseContractPolicy. Demo on integration status was presented last Thursday.

10-9-2025: Yellow

Work is continuing on the release pipeline. We have created a Jira card for CLOUDDST team to add destinations to Customer and Developer Portals. More stringent acceptance tests have been added to build pipeline (the same ones that will be used in release pipeline) and debugging is continuing. Need to identify how ISO will be presented in customer portal.
Show
10-15-2025: Yellow Changed to use a different releease pipeline - rh-advisories, on recommendation from CLOUDDST team to better accommodate the ISO when its pushed to Content Gateway and not expose as separate product. Refining ReleasePlanAdmission with feedback from CLOUDDST. Identified tests which will need to be excluded and added them to EnterpriseContractPolicy. Demo on integration status was presented last Thursday. 10-9-2025: Yellow Work is continuing on the release pipeline. We have created a Jira card for CLOUDDST team to add destinations to Customer and Developer Portals. More stringent acceptance tests have been added to build pipeline (the same ones that will be used in release pipeline) and debugging is continuing. Need to identify how ISO will be presented in customer portal.

Target Version:

openshift-4.20

SFDC Cases Links:
SFDC Cases Open:
SFDC Cases Counter:

Intelligence Requested:
Market:

Epic Goal

Setup an enterprise-grade build and release pipeline for the 4.20 TP OVE ISO artifact

Why is this important?

The OVE ISO will have to be released automatically for each z-stream ocp release, in order to allow any customer to use it as any other ocp release

Acceptance Criteria

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

Dependencies (internal and external)

The release pipeline will need to be discussed and agreed with the CLOUDDST team

Open questions::

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>