Uploaded image for project: 'OpenShift Cloud'
  1. OpenShift Cloud
  2. OCPCLOUD-1578

Design migration mechanism for MAPI to CAPI

XMLWordPrintable

    • Design migration mechanism for MAPI to CAPI
    • Product / Portfolio Work
    • OCPSTRAT-683Migrate MAPI to Cluster API for AWS (TP) - Phase 1
    • 0% To Do, 0% In Progress, 100% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • None
    • None
    • None

      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
      •  

              joelspeed Joel Speed
              rhn-support-dhardie Duncan Hardie
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: