-
Epic
-
Resolution: Done-Errata
-
Major
-
rhos-18.0.0
-
None
-
None
-
As a cloud operator I would like to adopt my existing 17.1 OpenStack environment that is running on Baremetal Control plane so that I am on a Red Hat supported platform & architecture.
-
2
-
False
-
-
False
-
OSPRH-3714Red Hat OpenStack 18.0 Data Plane Adoption [FR1]
-
Committed
-
No Docs Impact
-
To Do
-
OSPRH-3714 - Red Hat OpenStack 18.0 Data Plane Adoption [FR1]
-
openstack-operator-container-1.0.4-1
-
Committed
-
Committed
-
25% To Do, 0% In Progress, 75% Done
-
-
Enhancement
-
Done
-
Proposed
-
-
-
2024Q2
This epic outlines the goal for migrating from OpenStack Platform version 17.1 control plane running on baremetal to Red Hat OpenStack 18. This is distinct from the RHEV-based and Director-Operator-based process.
Goals
- Verify the adoption process for a non-RHEV and non-DirectorOperator environment. This could use virtual or real bare metal.
- Verify the adoption process for an environment that has a CephStorage role and Networker role in additional to a Compute role.
Topologies
Simple
This is the suggested topology for the component lines and for the developer workflow.
Source:
- 1 standalone (includes a single-node Ceph deployment)
Destination:
- 1 CRC
- 1 compute + single-node Ceph (previously standalone OpenStack + single-node Ceph)
Complex
This is the suggested topology for the integration line and possibly for architecture testing.
Source:
- 1 undercloud
- 3 controllers with HA fencing configured
- 3 computes (HCI)
- 1 networker
Destination:
- 3-node OCP (master+worker combined)
- 3 computes (HCI)
- 1 networker
Acceptance criteria
- Two jobs (one for each of the above topologies) in the in the openstack-periodic-container-antelope-centos9 line that exercises the latest podified-ci-testing content and which creates the new 'current-podified' when all required jobs have passed.
- links to
-
RHSA-2024:140345 RHOSO OpenStack Podified operator containers security update
- mentioned in
-
Page Loading...