-
Feature
-
Resolution: Unresolved
-
Major
-
rhos-18.0 FR 2 (Mar 2025)
-
None
-
RHOSSTRAT-904Reach Feature Complete Status for the Red Hat OpenStack Services on OpenShift 18.0 Adoption Process
-
Not Selected
-
False
-
False
-
-
0
-
0
-
0% To Do, 100% In Progress, 0% Done
Feature Overview
Enable upgrade of Red Hat OpenStack Platform (RHOSP) 17.1 environments with Instance HA enabled to RHOSO 18 using the adoption mechanism.
This allows customers relying on Instance HA (automatic evacuation and re-creation of instances on other compute nodes when a node fails) to adopt RHOSO, while being informed that HA functionality will be temporarily unavailable during a specific window in the adoption process.
Goals
The goal is to provide a validated upgrade path for RHOSP 17.1 deployments with Instance HA enabled, inform users that VM high availability will be temporarily disabled during adoption, and ensure that Instance HA resumes automatically and successfully post-adoption.
Who benefits from this Feature, and how?
- Cloud operators and administrators benefit by gaining a safe and supported migration path to RHOSO while using Instance HA.
- Customers with uptime SLAs can schedule and mitigate the temporary loss of HA during the upgrade window.
- Support teams can rely on clear documentation and tested procedures to assist customers during adoption.
Requirements
| Requirement | Notes | isMVP |
|---|---|---|
| Support Instance HA during RHOSP 17.1 to RHOSO 18 adoption | Validate adoption steps in an VM HA-enabled environment | Yes |
| Clearly document the temporary loss of VM HA during adoption | Critical for customer awareness and planning | Yes |
| Validate evacuation/fencing behavior post-adoption | Ensure proper HA function resumes | Yes |
Acceptance criteria:
- Documentation includes steps about how to disable Instance HA-enabled RHOSP 17.1
- Documentation clearly outlines the HA gap during adoption
- After the adoption procedure, RHOSO 18 instance HA is enabled as a Day2 operation. Fencing and evacuation resume and function normally after adoption
- Operator can validate that HA functionality is restored post-adoption
Use case example:
- Operator initiates adoption from RHOSP 17.1 with Instance HA enabled
- Operator follows supported adoption steps
- During a defined window, VM HA is temporarily unavailable
- Once adoption completes, Instance HA is restored
- Operator validates HA recovery and fencing behavior
Out of scope:
- Maintaining HA during the adoption window
- Supporting Instance HA adoption from RHOSP versions older than 17.1
- Cross-cloud migrations or mixed environments
- Non-pacemaker-based RHOSP 17.1 HA configurations
Documentation considerations:
- Add adoption-specific warning and behavior to Instance HA documentation
- Include a dedicated section in the RHOSP to RHOSO adoption guide about HA
- Include post-adoption validation steps for HA
Open questions:
