Goal

As documented in OCPCLOUD-1578, OpenShift would like to migrate from Machine API to Cluster API and eventually remove Machine API. This effort is going to require work from all affected platforms including OpenStack. This epic tracks the implementation of the OpenStack part of the mapi2capi and capi2mapi translation layer being added to cluster-capi-operator, based on the scoping done in OSASINFRA-3440.

Note that it is important that we implement both MAPI to CAPI and CAPI to MAPI for all platforms including OpenStack. This ensures we will always have a mirror copy on both sides, which is particularly useful for third-party components that don't have a way to interact with CAPI yet. In these situations, users can create CAPI resources while these components can (until updated) continue to fetch the MAPI mirror and work out the state of the cluster that way.

Why is this important?

Repeating from OCPCLOUD-1578:

• 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

From an OpenStack perspective, we simply need to ensure we follow suit with other platforms.

Scenarios

• Given an existing deployment being upgraded to 4.18, we should automatically translate the existing MAPO resources to CAPO resources.

Acceptance Criteria

• Patches merged to openshift/cluster-capi-operator
• CI - MUST be running successfully with tests automated
• Release Technical Enablement
• ...

Dependencies (internal and external)

TBD.

Previous Work (Optional):

• OSASINFRA-3440

Open questions::

TBD.