Details
-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Document how to make Machine API work with UPI
-
False
-
False
-
To Do
-
OCPSTRAT-34 - Machine API (Phase 6)
-
-
40
-
40%
-
Undefined
Description
Epic Goal
- Remove existing documentation in UPI install flow that instructs users to remove machineset manifests
- Document requirements for users to update their machinesets to enable them to work with Machine API
- Provide escape hatch for UPI users who do not want to use Machine API (separate page about how to remove manifests pre/post install)
- Ensure risks of using UPI and MAPI together are documented
Why is this important?
- We would like to reduce the difference between UPI and IPI clusters
- UPI users should not be excluded from using Machine API
- Conversation originated in https://bugzilla.redhat.com/show_bug.cgi?id=1834966
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
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>
Attachments
Issue Links
- is related to
-
OCPBUGS-1226 OpenStack UPI scripts do not create server group for Computes
-
- Closed
-
- links to
1.
|
TE Tracker |
|
Closed | 
|
Unassigned |
2.
|
Docs Tracker |
|
Closed |
|
Unassigned |
3.
|
QE Tracker |
|
Closed |
|
Unassigned |
