-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
Feature Overview (aka. Goal Summary)
Hosted control planes are a key technology already available on IBM Z systems where the control plane is x86 and the node pools (compute nodes) are IBM Z. This feature would look to reverse that situation with a IBM Z control plane and node pools made up of x86 systems.
This is desirable for users who want high resilience and DR capabilities built into a mission critical control plane while leveraging x86 systems for their workloads.
Goals (aka. expected user outcomes)
HCP support for IBM Z control plane and node pools made up of x86 systems
Requirements (aka. Acceptance Criteria):
HCP support for IBM Z control plane and node pools made up of x86 systems
Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.
Deployment considerations | List applicable specific needs (N/A = not applicable) |
Self-managed, managed, or both | n/a |
Classic (standalone cluster) | n/a |
Hosted control planes | Yes |
Multi node, Compact (three node), or Single node (SNO), or all | n/a |
Connected / Restricted Network | Yes |
Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | IBM Z and x86 |
Operator compatibility | n/a |
Backport needed (list applicable versions) | No |
UI need (e.g. OpenShift Console, dynamic plugin, OCM) | n/a |
Other (please specify) | n/a |
Use Cases (Optional):
Include use case diagrams, main success scenarios, alternative flow scenarios. Initial completion during Refinement status.
<your text here>
Questions to Answer (Optional):
Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.
<your text here>
Out of Scope
High-level list of items that are out of scope. Initial completion during Refinement status.
<your text here>
Background
Provide any additional context is needed to frame the feature. Initial completion during Refinement status.
<your text here>
Customer Considerations
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature. Initial completion during Refinement status.
<your text here>
Documentation Considerations
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.
<your text here>
Interoperability Considerations
Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact? What interoperability test scenarios should be factored by the layered products? Initial completion during Refinement status.
<your text here>
- relates to
-
ACM-22743 [PICS] ACM 2.15.0 - Fresh Install + E2E regression on IBM Z hub on OCP 4.20
-
- Closed
-