Feature Overview
This features describles the upgrade from Red Hat OpenStack Platform (RHOSP) 17.1 deployed using Director Operator to Red Hat OpenStack Services on OpenShift using the Adoption Mechanism. This approach enables a phased, side-by-side upgrade for the control plane running in the same cluster of OpenShift and an in-place upgrade for the data plane, ensuring minimal disruption and providing a rollback option.

Goals
Who benefits from this feature, and how?

• Cloud Administrators benefit from increased flexibility, scalability, and manageability of the OpenStack control plane running 100% podified in OpenShift

What is the difference between today's current state and a world with this feature?

Current State: The OpenStack control plane runs as containers in RHEL virtual machines hosted in OpenShift Virtualization.
Future State with This Feature: The control plane runs as pods in an OpenShift cluster on CoreOS.

Requirements
A list of specific needs or objectives that a Feature must deliver to satisfy the Feature.. Some requirements will be flagged as MVP. If an MVP gets shifted, the feature shifts. If a non MVP requirement slips, it does not shift the feature.

Assumptions
The operator runing the upgrade does not need additional hardware to run the Adotion-based upgrade.

Customer Considerations
The operator runing the upgrade does not need additional hardware to run the Adotion-based upgrade.

Documentation Considerations
New Content and Updates to existing content to describe the procedure.

Interoperability Considerations
This procedure should be compatible with TNC 3.0 reference architecture. Telco Network Cloud Reference Architecture V3.0

Questions