Define OpenStackDataPlaneNodeSet custom resources (CRs) to group your RHEL 9.4 or 9.6 compute nodes by type, configuration, and role, creating the data plane layout for your cloud workloads.

You can use pre-provisionedsssss or unprovisioned nodes in an OpenStackDataPlaneNodeSet CR:

• Pre-provisioned node: You have used your own tools to install the operating system on the node before adding it to the data plane.
• Unprovisioned node: The node does not have an operating system installed before you add it to the data plane. The node is provisioned by using the Cluster Baremetal Operator (CBO) as part of the data plane creation and deployment process.

To create and deploy a data plane, you must perform the following tasks:

1. Create a Secret CR for each node set for Ansible to use to run commands on the data plane nodes.
2. Create the OpenStackDataPlaneNodeSet CRs that define the nodes and layout of the data plane.
3. Create the OpenStackDataPlaneDeployment CR that triggers the Ansible execution that deploys and configures the software for the specified list of OpenStackDataPlaneNodeSet CRs.

The following procedures create two simple node sets, one with pre-provisioned nodes, and one with bare-metal nodes that must be provisioned during the node set deployment. The procedures aim to get you up and running quickly with a data plane environment that you can use to troubleshoot issues and test the environment before adding all the customizations you require. You can add additional node sets to a deployed environment, and you can customize your deployed environment by updating the common configuration in the default ConfigMap CR for the service, and by creating custom services.