-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
Design migration mechanism for MAPI to CAPI
-
BU Product Work
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-683 - Migrate MAPI to Cluster API for AWS -Phase 1
-
OCPSTRAT-683Migrate MAPI to Cluster API for AWS -Phase 1
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
- There is a need to provide a way to convert from using the Machine API (MAPI) to Cluster API (CAPI).
- This Epic is to investigate possible solutions with the output being a report and an architecture on how the solution will be implemented
- The Epic should also result in a plan (with a phased approach if necessary) of how the components are delivered
Why is this important?
- MAPI is widely used and as OpenShift switches over to using CAPI we need a painless and simple way to get our users over to using CAPI
- Users should either not notice, or not care that the migration has occurred
- Must ensure a smooth and staged migration with provider migration being independent from one another
Acceptance Criteria
- enhancement PR merged
- blocks
-
OCPCLOUD-2120 Implement Migration core for MAPI to CAPI
- In Progress
- links to