-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
2023Q1
In order to show progress towards our OSP 18.0 release, the following should be demonstrated. This is not meant to be an exhaustive list of features/functionality to demonstrate. It is the minimum expectation.
Any work items (Spikes, Stories, Tasks, etc) that relate to achieving this should be related to this Epic through JIRA links (incorporates, is blocked by, relates to, depends on, etc).
Greenfield Deployment
Given:
- A pre-provisioned OpenShift Cluster
- A set of pre-provisioned data plane nodes
- A pre-provisioned Ceph cluster
Demonstrate:
- Deploy OpenStack control plane services using the OpenStack (meta) Operator (OSP-17711).
- Deploy OpenStack data plane services using the Dataplane CRD (OSP-20001).
- The implementation of both infrastructure (eg: ntp) and OpenStack (eg: nova-compute) services on the data plane.
- Via the OpenStack client, boot a VM from a Cinder-provided volume on the Ceph cluster using an image from Glance. Then connect to it via ssh using a floating IP address.
Stretch goals:
- Deploy a custom configuration (something like CPU pinning) which results in changes on a data plane host
- Provision the data plane nodes with the Baremetal Provisioning CRD (
OSP-21264) - Use HCI - Ceph running on EDPM computes; collocated but logically external (
OSP-21366) - Demonstrate shared filesystem (Manila) basic functionalities (
OSP-20089)
CI Modernization
Demonstrate:
- What kinds of CI tests get run where in the new production chain
- What each test type looks like in action (including where to find logs, etc)
- How to contribute to each kind of test
Adoption
Demonstrate:
- The adoption of one or more control plane services using the adjusted process after the 'all in on next-gen' decision
Stretch goal:
- Demonstrate the implementation of the Adoption process in CI for one or more control plane services
- is blocked by
-
OSPRH-2053 Create a document with Adoption problems + possible solutions coming from dropping OSP 18 Director
- Closed
-
OSPRH-3243 [ovn-operator] Investigate how to expose SB DBs to compute nodes
- Closed
-
OSPRH-3251 [ovs-operator] Connect ovs pod to the tunnel networks
- Closed
-
OSPRH-1218 Glance Adoption with Ceph backend
- Closed
-
OSPRH-2049 Connect Keystone to adopted MariaDB
- Closed
-
OSPRH-2051 Update Adoption docs for "FFUdoption" variant
- Closed
-
OSPRH-2058 Bootstrap Adoption test suite
- Closed
-
OSPRH-2059 Extend Adoption test suite with Keystone, Glance, Placement
- Closed
-
OSPRH-2046 Add services which succeed to deploy in the adopted cloud
- Closed
-
OSPRH-2055 Prevent MariaDB state divergence between old vs. podified
- Closed
-
OSPRH-1295 Prepare 2023 Q1 Greenfield Demo
- Closed
-
OSPRH-2096 2023 Q1 Adoption demo prep
- Closed
-
OSPRH-1294 Prepare 2023 Q1 EDPM Demo
- Closed
- is related to
-
OSPRH-6473 Meta (umbrella) Operator
- In Progress
-
OSPRH-2398 As a cloud operator, I would like to deploy my external data plane hosts from bare metal, so that I can deploy and manage them through a single interface.
- Closed
-
OSPRH-1582 [DEV] Configure Client Ceph on external data plane
- Closed
-
OSPRH-3222 [neutron-operator] Add controller for neutron-dhcp-agent
- Closed
-
OSPRH-3233 [neutron-operator] Add controller to deploy neutron-ovn-metadata-agent
- Closed
-
OSPRH-1591 Boostrap Swift operator, deploying all components in OCP
- Closed
-
OSPRH-1116 Create Manila operator skeleton
- Closed
-
OSPRH-3266 Consider combining ovs-operator and ovn-operator into a single operator
- Closed
-
OSPRH-2431 Neutron with OVN adoption try
- Closed
- relates to
-
OSPRH-3223 [neutron-operator] Generate ConfigMaps for the AnsibleEE operator
- Closed
-
OSPRH-4162 Allow services to be connected to isolated networks
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...