Epic Goal

• Deliver HyperShift functionality for the IBM zSystems architecture
• This epic will be limited to having an x86 control plane with zSystem compute nodes

Why is this important?

• Customers want to use resources effectively and it has been noted that it can be more cost effective to have a control plane of x86 nodes matched with workloads that run on IBM zSystem compute nodes

Functional Team:
PM - Duncan Hardie
PX - Jon Thomas
RH Dev - Jeremy Poulin
Z Dev - Rishika Kedia, Vikas Singh
Z QE - Florian Leber
Z Docs - Silke Niemann

Contacts:
x86 PM - Adel Zaalouk
x86 Lead - Alberto Lamela
x86 QE - Jie Zhao
x86 PX - Dave Mulford
x86 Docs - Laura Hinson
Main Channel - #project-hypershift

Scenarios
1. …

Acceptance Criteria

• (Enter a list of Acceptance Criteria unique to the Epic)
• …

Dependencies (internal and external)
1. …

Previous Work (Optional):
1. …

Open questions::
1. …

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
• Release Enablement: <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
• QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
• QE - Automated tests merged: <link or reference to automated tests>
• QE - QE to verify documentation when testing
• DOC - Downstream documentation merged: <link to meaningful PR>
• All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.