Deliver the OSP Director Operator as a Fully Supported in OSP 17.0 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.
closing for the moment, it can be reopened once we figure out plan and timing
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days