Deliver the OSP Director Operator as a Tech Preview in OSP 16.2 The OSP Director Operator creates a set of Custom Resource Definitions (CRDs) on top of OpenShift to manage resources normally created by the TripleO's Undercloud. CRDs are split into two types for hardware provisioning and software configuration which aligns well with TripleO's Undercloud Lite architecture. The Operator includes CRDs to create and manage Overcloud Nets (IPAM), VMSets (for OSP Controllers), and BaremetalSets (for OSP Computes). For Tech Preview (small scale demo deployments) Software configuration is accomplished via an OpenStackClient pod using traditional OSP/TripleO interfaces and CLI commands. Work is ongoing to produce a more scalable Heat to Ansible Playbook deployment workflow within the OSP Director Operator.
Containers needed for this -------- openstack-tripleoclient-container operator operator-bundle tripleoclient change is already in
This RFE is tech preview with no QE resources assigned to the project. No expectation of polarion reporting automated tests unless resources are assigned to make that happen.
greg, the only edit i would make is removing 'which aligns well with the RHOSP undercloud lite architecture.' In my opinion, this concept isn't externally visible at this point. It may create confusion and/or require more explanation which wouldn't provide much value at this time. Should the architecture changes realize our ambitions, it may be a thing PM wants to sell going forward.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of containers for Red Hat OpenStack 16.2 director operator tech preview), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2021:3486