-
Spike
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
-
False
-
None
-
None
-
None
-
None
Spike Goal:
There are two items which needs to be covered as part of this spike
1. Design of alternative solution for LPAR (in PR/SM mode)
- For IBM Z LPAR(in PR/SM mode) with OSA network card ,mac addresses are not persistent across reboots. We need to find a solution for this and implement in the Agent based installer where the IP asssignment and role allocation is tightly coupled with the Mac Address.
- follow-up epic should include: Implementation of the agreed solution, Validation of the new functionality
- Goal of the Spike is to find the alternative design for this particular case to bring in parity with other installers as because of the inpersistent Mac Address currently OCP HA cluster installation on LPAR (PR/SM mode) not supported with OSA.
- Identify all dependencies and required information for epic (potentially 4.22).
2. Validations of VLAN, bonding and multiple interfaces
- Other activity to be covered as part of this epic is to validate VLAN tagging and bonding mode.
- Validate multiple interfaces for the OCP install with ABI.
Why is this important?
- Close gaps in possible configurations and installation methods for IBM Z and IBM LinuxONE
- To bring in the consistent installation expericence through ABI for all the network cards and hypervisors.
Spike Size: M
Scenarios
1. …
Acceptance Criteria
- Design discussed and agreed by RH ABI team.
- Creation of test matrix across it.
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'.