Define the procedure and develop any necessary tooling to adopt a Director-deployed Nova Control Plane and Data Plane into a Podified Control Plane.

Goals:

Placement
Stretch goals:

Placement 17.1 -> 18.x FFUdoption
Properties:

Source: Standalone deployment of OSP 18.0 (or stable/zed) (stretched: 17.1/wallaby)
Destination:
CRC or SNO with Podified Control Plane
stable/zed tripleo-ansible content for Ansible Execution Environment
Demonstrable manual steps to do the adoption (no FFU included)
Basic test environment for dev purposes
At this stage we do not need to be concerned about transitional data or transactions in flight. not going 17.1 to 18.x (FFUdoption)
Timelines:

2022 Q3 - 2023 Q1
Definition of Done:

Placement: Demonstrate the complete service transition from source to destination
TBD: exact steps: showing endpoints, placement CLIs?
When this task is complete, we will be able to demonstrate scaling update Placement -> OCP, scaling down the ‘old’ Placement, and moving its DB traffic to OCP. Placement will be running entirely self-sufficiently on OCP (but with the same source version of Placement, i.e. 17.x wallaby, or 18.x master/zed).

https://openstack-k8s-operators.github.io/data-plane-adoption/openstack/placement_adoption/