Chapter 5. Creating the data plane The Red Hat OpenStack Services on OpenShift (RHOSO) data plane consists of RHEL 9.4 nodes. Use the OpenStackDataPlaneNodeSet custom resource definition (CRD) to create the custom resources (CRs) that define the nodes and the layout of the data plane. An OpenStackDataPlaneNodeSet CR is a logical grouping of nodes of a similar type. A data plane typically consists of multiple OpenStackDataPlaneNodeSet CRs to define groups of nodes with different configurations and roles. You can use pre-provisioned or unprovisioned nodes in an OpenStackDataPlaneNodeSet CR: Pre-provisioned node: You have used your own tooling 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. Note You cannot include both pre-provisioned and unprovisioned nodes in the same OpenStackDataPlaneNodeSet CR. To create and deploy a data plane, you must perform the following tasks: Create a Secret CR for each node set for Ansible to use to execute commands on the data plane nodes. Create the OpenStackDataPlaneNodeSet CRs that define the nodes and layout of the data plane. 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. For more information about how to customize your data plane after deployment, see the Customizing the Red Hat OpenStack Services on OpenShift deployment guide. 5.1. Prerequisites A functional control plane, created with the OpenStack Operator. For more information, see Creating the control plane . You are logged on to a workstation that has access to the Red Hat OpenShift Container Platform (RHOCP) cluster as a user with cluster-admin privileges. 5.2. Creating the data plane secrets The data plane requires several Secret custom resources (CRs) to operate. The Secret CRs are used by the data plane nodes for the following functionality: To enable secure access between nodes: You must generate an SSH key and create an SSH key Secret CR for each key to enable Ansible to manage the RHEL nodes on the data plane. Ansible executes commands with this user and key. You can create an SSH key for each node set in your data plane. You must generate an SSH key and create an SSH key Secret CR for each key to enable migration of instances between Compute nodes. To register the operating system of the nodes that are not registered to the Red Hat Customer Portal. To enable repositories for the nodes. To provide access to libvirt. Prerequisites Pre-provisioned nodes are configured with an SSH public key in the USDHOME/.ssh/authorized_keys file for a user with passwordless sudo privileges. For information, see Configuring reserved user and group IDs in the RHEL Configuring basic system settings guide. Procedure For unprovisioned nodes, create the SSH key pair for Ansible: Replace <key_file_name> with the name to use for the key pair. Create the Secret CR for Ansible and apply it to the cluster: Replace <key_file_name> with the name and location of your SSH key pair file. Optional: Only include the --from-file=authorized_keys option for bare-metal nodes that must be provisioned when creating the data plane. Create the SSH key pair for instance migration: Create the Secret CR for migration and apply it to the cluster: Create a file on your workstation named secret_subscription.yaml that contains the subscription-manager credentials for registering the operating system of the nodes that are not registered to the Red Hat Customer Portal: Replace <base64_username> and <base64_password> with strings that are base64-encoded. You can use the following command to generate a base64-encoded string: Tip If you don't want to base64-encode the username and password, you can use the stringData field instead of the data field to set the username and password. Create the Secret CR: Create a Secret CR that contains the Red Hat registry credentials: Replace <username> and <password> with your Red Hat registry username and password credentials. For information about how to create your registry service account, see the Knowledge Base article Creating Registry Service Accounts . Create a file on your workstation named secret_libvirt.yaml to define the libvirt secret: Replace <base64_password> with a base64-encoded string with maximum length 63 characters. You can use the following command to generate a base64-encoded password: Tip If you do not want to base64-encode the username and password, you can use the stringData field instead of the data field to set the username and password. Create the Secret CR: Verify that the Secret CRs are created: 5.3. Creating an OpenStackDataPlaneNodeSet CR with pre-provisioned nodes Define an OpenStackDataPlaneNodeSet custom resource (CR) for each logical grouping of pre-provisioned nodes in your data plane, for example, nodes grouped by hardware, location, or networking. You can define as many node sets as necessary for your deployment. Each node can be included in only one OpenStackDataPlaneNodeSet CR. Each node set can be connected to only one Compute cell. By default, node sets are connected to cell1 . If you customize your control plane to include additional Compute cells, you must specify the cell to which the node set is connected. For more information on adding Compute cells, see Connecting an OpenStackDataPlaneNodeSet CR to a Compute cell in the Customizing the Red Hat OpenStack Services on OpenShift deployment guide. You use the nodeTemplate field to configure the common properties to apply to all nodes in an OpenStackDataPlaneNodeSet CR, and the nodeTemplate.nodes field for node-specific properties. Node-specific configurations override the inherited values from the nodeTemplate . Tip For an example OpenStackDataPlaneNodeSet CR that a node set from pre-provisioned Compute nodes, see Example OpenStackDataPlaneNodeSet CR for pre-provisioned nodes . Procedure Create a file on your workstation named openstack_preprovisioned_node_set.yaml to define the OpenStackDataPlaneNodeSet CR: 1 The OpenStackDataPlaneNodeSet CR name must be unique, contain only lower case alphanumeric characters and - (hyphens) or . (periods), start and end with an alphanumeric character, and have a maximum length of 53 characters. Update the name in this example to a name that reflects the nodes in the set. 2 Optional: A list of environment variables to pass to the pod. Connect the data plane to the control plane network: Specify that the nodes in this set are pre-provisioned: Add the SSH key secret that you created to enable Ansible to connect to the data plane nodes: Replace <secret-key> with the name of the SSH key Secret CR you created for this node set in Creating the data plane secrets , for example, dataplane-ansible-ssh-private-key-secret . Create a Persistent Volume Claim (PVC) in the openstack namespace on your Red Hat OpenShift Container Platform (RHOCP) cluster to store logs. Set the volumeMode to Filesystem and accessModes to ReadWriteOnce . Do not request storage for logs from a PersistentVolume (PV) that uses the NFS volume plugin. NFS is incompatible with FIFO and the ansible-runner creates a FIFO file to write to store logs. For information about PVCs, see Understanding persistent storage in the RHOCP Storage guide and Red Hat OpenShift Container Platform cluster requirements in Planning your deployment . Enable persistent logging for the data plane nodes: Replace <pvc_name> with the name of the PVC storage on your RHOCP cluster. Specify the management network: Specify the Secret CRs used to source the usernames and passwords to register the operating system of the nodes that are not registered to the Red Hat Customer Portal, and enable repositories for your nodes. The following example demonstrates how to register your nodes to Red Hat Content Delivery Network (CDN). For information about how to register your nodes with Red Hat Satellite 6.13, see Managing Hosts . 1 The user associated with the secret you created in Creating the data plane secrets . 2 The Ansible variables that customize the set of nodes. For a list of Ansible variables that you can use, see https://openstack-k8s-operators.github.io/edpm-ansible/ . 3 Optional: If you have multiple Red Hat subscriptions and want to attach a specific pool to your subscription to register the nodes, replace <pool_id> with the pool ID you want to register. For a complete list of the Red Hat Customer Portal registration commands, see https://access.redhat.com/solutions/253273 . For information about how to log into registry.redhat.io , see https://access.redhat.com/RegistryAuthentication#creating-registry-service-accounts-6 . Add the network configuration template to apply to your data plane nodes. The following example applies the single NIC VLANs network configuration to the data plane nodes: 1 Update the nic1 field to the MAC address assigned to the NIC to use for network configuration on the Compute node. 2 Set the edpm_network_config_update variable to true to apply any updates you make to the network configuration after the node set is deployed. Note You must reset the edpm_network_config_update variable to false after the updated network configuration is applied in a new OpenStackDataPlaneDeployment CR, otherwise the updated network configuration is reapplied every time an OpenStackDataPlaneDeployment CR is created that includes the configure-network service. For more information about data plane network configuration, see Customizing data plane networks in Configuring network services . Add the common configuration for the set of nodes in this group under the nodeTemplate section. Each node in this OpenStackDataPlaneNodeSet inherits this configuration. For information about the properties you can use to configure common node attributes, see OpenStackDataPlaneNodeSet CR spec properties . Define each node in this node set: 1 The node definition reference, for example, edpm-compute-0 . Each node in the node set must have a node definition. 2 Defines the IPAM and the DNS records for the node. 3 Specifies a predictable IP address for the network that must be in the allocation range defined for the network in the NetConfig CR. 4 Node-specific Ansible variables that customize the node. Note Nodes defined within the nodes section can configure the same Ansible variables that are configured in the nodeTemplate section. Where an Ansible variable is configured for both a specific node and within the nodeTemplate section, the node-specific values override those from the nodeTemplate section. You do not need to replicate all the nodeTemplate Ansible variables for a node to override the default and set some node-specific values. You only need to configure the Ansible variables you want to override for the node. Many ansibleVars include edpm in the name, which stands for "External Data Plane Management". For information about the properties you can use to configure node attributes, see OpenStackDataPlaneNodeSet CR properties . Save the openstack_preprovisioned_node_set.yaml definition file. Create the data plane resources: Verify that the data plane resources have been created by confirming that the status is SetupReady : When the status is SetupReady the command returns a condition met message, otherwise it returns a timeout error. For information about the data plane conditions and states, see Data plane conditions and states . Verify that the Secret resource was created for the node set: Verify the services were created: 5.3.1. Example OpenStackDataPlaneNodeSet CR for pre-provisioned nodes The following example OpenStackDataPlaneNodeSet CR creates a node set from pre-provisioned Compute nodes with some node-specific configuration. Update the name of the OpenStackDataPlaneNodeSet CR in this example to a name that reflects the nodes in the set. The OpenStackDataPlaneNodeSet CR name must be unique, contain only lower case alphanumeric characters and - (hyphens) or . (periods), start and end with an alphanumeric character, and have a maximum length of 53 characters. Update the name in this example to a name that reflects the nodes in the set. 5.4. Creating a data plane with unprovisioned nodes To create a data plane with unprovisioned nodes, you must perform the following tasks: Create a BareMetalHost custom resource (CR) for each bare-metal data plane node. Define an OpenStackDataPlaneNodeSet CR for each logical grouping of unprovisioned nodes in your data plane, for example, nodes grouped by hardware, location, or networking. Prerequisites Your RHOCP cluster supports provisioning bare-metal nodes. For more information, see Planning provisioning for bare-metal data plane nodes in Planning your deployment . Your Cluster Baremetal Operator (CBO) is configured for provisioning. For more information, see Provisioning [metal3.io/v1alpha1 ] in the RHOCP API Reference . 5.4.1. Creating the BareMetalHost CRs for unprovisioned nodes You must create a BareMetalHost custom resource (CR) for each bare-metal data plane node. At a minimum, you must provide the data required to add the bare-metal data plane node on the network so that the remaining installation steps can access the node and perform the configuration. Note If you use the ctlplane interface for provisioning, to avoid the kernel rp_filter logic from dropping traffic, configure the DHCP service to use an address range different from the ctlplane address range. This ensures that the return traffic remains on the machine network interface. Procedure The Bare Metal Operator (BMO) manages BareMetalHost custom resources (CRs) in the openshift-machine-api namespace by default. Update the Provisioning CR to watch all namespaces: If you are using virtual media boot for bare-metal data plane nodes and the nodes are not connected to a provisioning network, you must update the Provisioning CR to enable virtualMediaViaExternalNetwork , which enables bare-metal connectivity through the external network: Create a file on your workstation that defines the Secret CR with the credentials for accessing the Baseboard Management Controller (BMC) of each bare-metal data plane node in the node set: Replace <base64_username> and <base64_password> with strings that are base64-encoded. You can use the following command to generate a base64-encoded string: Tip If you do not want to base64-encode the username and password, you can use the stringData field instead of the data field to set the username and password. Create a file named bmh_nodes.yaml on your workstation, that defines the BareMetalHost CR for each bare-metal data plane node. The following example creates a BareMetalHost CR with the provisioning method Redfish virtual media: 1 The URL for communicating with the node's BMC controller. For information about BMC addressing for other provisioning methods, see BMC addressing in the RHOCP Deploying installer-provisioned clusters on bare metal guide. 2 The name of the Secret CR you created in the step for accessing the BMC of the node. 3 Optional: The name of the network configuration secret in the local namespace to pass to the pre-provisioning image. The network configuration must be in nmstate format. For more information about how to create a BareMetalHost CR, see About the BareMetalHost resource in the RHOCP Postinstallation configuration guide. Create the BareMetalHost resources: Verify that the BareMetalHost resources have been created and are in the Available state: 5.4.2. Creating an OpenStackDataPlaneNodeSet CR with unprovisioned nodes Define an OpenStackDataPlaneNodeSet custom resource (CR) for each logical grouping of unprovisioned nodes in your data plane, for example, nodes grouped by hardware, location, or networking. You can define as many node sets as necessary for your deployment. Each node can be included in only one OpenStackDataPlaneNodeSet CR. Each node set can be connected to only one Compute cell. By default, node sets are connected to cell1 . If you customize your control plane to include additional Compute cells, you must specify the cell to which the node set is connected. For more information on adding Compute cells, see Connecting an OpenStackDataPlaneNodeSet CR to a Compute cell in the Customizing the Red Hat OpenStack Services on OpenShift deployment guide. You use the nodeTemplate field to configure the common properties to apply to all nodes in an OpenStackDataPlaneNodeSet CR, and the nodeTemplate.nodes field for node-specific properties. Node-specific configurations override the inherited values from the nodeTemplate . Tip For an example OpenStackDataPlaneNodeSet CR that creates a node set from unprovisioned Compute nodes, see Example OpenStackDataPlaneNodeSet CR for unprovisioned nodes . Prerequisites A BareMetalHost CR is created for each unprovisioned node that you want to include in each node set. For more information, see Creating the BareMetalHost CRs for unprovisioned nodes . Procedure Create a file on your workstation named openstack_unprovisioned_node_set.yaml to define the OpenStackDataPlaneNodeSet CR: 1 The OpenStackDataPlaneNodeSet CR name must be unique, contain only lower case alphanumeric characters and - (hyphens) or . (periods), start and end with an alphanumeric character, and have a maximum length of 53 characters. Update the name in this example to a name that reflects the nodes in the set. 2 Optional: A list of environment variables to pass to the pod. Connect the data plane to the control plane network: Specify that the nodes in this set are unprovisioned and must be provisioned when creating the resource: Define the baremetalSetTemplate field to describe the configuration of the bare-metal nodes that must be provisioned when creating the resource: Replace <bmh_namespace> with the namespace defined in the corresponding BareMetalHost CR for the node, for example, openshift-machine-api . Replace <ansible_ssh_user> with the username of the Ansible SSH user, for example, cloud-admin . Replace <bmh_label> with the label defined in the corresponding BareMetalHost CR for the node, for example, openstack . Replace <interface> with the control plane interface the node connects to, for example, enp6s0 . If you created a custom OpenStackProvisionServer CR, add it to your baremetalSetTemplate definition: Add the SSH key secret that you created to enable Ansible to connect to the data plane nodes: Replace <secret-key> with the name of the SSH key Secret CR you created in Creating the data plane secrets , for example, dataplane-ansible-ssh-private-key-secret . Create a Persistent Volume Claim (PVC) in the openstack namespace on your Red Hat OpenShift Container Platform (RHOCP) cluster to store logs. Set the volumeMode to Filesystem and accessModes to ReadWriteOnce . Do not request storage for logs from a PersistentVolume (PV) that uses the NFS volume plugin. NFS is incompatible with FIFO and the ansible-runner creates a FIFO file to write to store logs. For information about PVCs, see Understanding persistent storage in the RHOCP Storage guide and Red Hat OpenShift Container Platform cluster requirements in Planning your deployment . Enable persistent logging for the data plane nodes: Replace <pvc_name> with the name of the PVC storage on your RHOCP cluster. Specify the management network: Specify the Secret CRs used to source the usernames and passwords to register the operating system of the nodes that are not registered to the Red Hat Customer Portal, and enable repositories for your nodes. The following example demonstrates how to register your nodes to Red Hat Content Delivery Network (CDN). For information about how to register your nodes with Red Hat Satellite 6.13, see Managing Hosts . 1 The user associated with the secret you created in Creating the data plane secrets . 2 The Ansible variables that customize the set of nodes. For a list of Ansible variables that you can use, see https://openstack-k8s-operators.github.io/edpm-ansible/ . 3 Optional: If you have multiple Red Hat subscriptions and want to attach a specific pool to your subscription to register the nodes, replace <pool_id> with the pool ID you want to register. For a complete list of the Red Hat Customer Portal registration commands, see https://access.redhat.com/solutions/253273 . For information about how to log into registry.redhat.io , see https://access.redhat.com/RegistryAuthentication#creating-registry-service-accounts-6 . Add the network configuration template to apply to your data plane nodes. The following example applies the single NIC VLANs network configuration to the data plane nodes: 1 Update the nic1 to the MAC address assigned to the NIC to use for network configuration on the Compute node. 2 Set the edpm_network_config_update variable to true to apply any updates you make to the network configuration after the node set is deployed. Note You must reset the edpm_network_config_update variable to false after the updated network configuration is applied in a new OpenStackDataPlaneDeployment CR, otherwise the updated network configuration is reapplied every time an OpenStackDataPlaneDeployment CR is created that includes the configure-network service. For more information about data plane network configuration, see Customizing data plane networks in Configuring network services . Add the common configuration for the set of nodes in this group under the nodeTemplate section. Each node in this OpenStackDataPlaneNodeSet inherits this configuration. For information about the properties you can use to configure common node attributes, see OpenStackDataPlaneNodeSet CR properties . Define each node in this node set: 1 The node definition reference, for example, edpm-compute-0 . Each node in the node set must have a node definition. 2 Defines the IPAM and the DNS records for the node. 3 Specifies a predictable IP address for the network that must be in the allocation range defined for the network in the NetConfig CR. 4 Optional: The Secret that contains network configuration that is node-specific. 5 Optional: The Secret that contains user data that is node-specific. 6 Node-specific Ansible variables that customize the node. 7 Optional: The BareMetalHost CR label that selects the BareMetalHost CR for the data plane node. The label can be any label that is defined for the BareMetalHost CR. The label is used with the bmhLabelSelector label configured in the baremetalSetTemplate definition to select the BareMetalHost for the node. Note Nodes defined within the nodes section can configure the same Ansible variables that are configured in the nodeTemplate section. Where an Ansible variable is configured for both a specific node and within the nodeTemplate section, the node-specific values override those from the nodeTemplate section. You do not need to replicate all the nodeTemplate Ansible variables for a node to override the default and set some node-specific values. You only need to configure the Ansible variables you want to override for the node. Many ansibleVars include edpm in the name, which stands for "External Data Plane Management". For information about the properties you can use to configure node attributes, see OpenStackDataPlaneNodeSet CR properties . Save the openstack_unprovisioned_node_set.yaml definition file. Create the data plane resources: Verify that the data plane resources have been created by confirming that the status is SetupReady : When the status is SetupReady the command returns a condition met message, otherwise it returns a timeout error. For information about the data plane conditions and states, see Data plane conditions and states . Verify that the Secret resource was created for the node set: Verify that the nodes have transitioned to the provisioned state: Verify that the services were created: 5.4.3. Example OpenStackDataPlaneNodeSet CR for unprovisioned nodes The following example OpenStackDataPlaneNodeSet CR creates a node set from unprovisioned Compute nodes with some node-specific configuration. The unprovisioned Compute nodes are provisioned when the node set is created. Update the name of the OpenStackDataPlaneNodeSet CR in this example to a name that reflects the nodes in the set. The OpenStackDataPlaneNodeSet CR name must be unique, contain only lower case alphanumeric characters and - (hyphens) or . (periods), start and end with an alphanumeric character, and have a maximum length of 53 characters. Update the name in this example to a name that reflects the nodes in the set. 5.5. OpenStackDataPlaneNodeSet CR spec properties The following sections detail the OpenStackDataPlaneNodeSet CR spec properties you can configure. 5.5.1. nodeTemplate Defines the common attributes for the nodes in this OpenStackDataPlaneNodeSet . You can override these common attributes in the definition for each individual node. Table 5.1. nodeTemplate properties Field Description ansibleSSHPrivateKeySecret Name of the private SSH key secret that contains the private SSH key for connecting to nodes. Secret name format: Secret.data.ssh-privatekey For more information, see Creating an SSH authentication secret . Default: dataplane-ansible-ssh-private-key-secret managementNetwork Name of the network to use for management (SSH/Ansible). Default: ctlplane networks Network definitions for the OpenStackDataPlaneNodeSet . ansible Ansible configuration options. For more information, see ansible properties . extraMounts The files to mount into an Ansible Execution Pod. userData UserData configuration for the OpenStackDataPlaneNodeSet . networkData NetworkData configuration for the OpenStackDataPlaneNodeSet . 5.5.2. nodes Defines the node names and node-specific attributes for the nodes in this OpenStackDataPlaneNodeSet . Overrides the common attributes defined in the nodeTemplate . Table 5.2. nodes properties Field Description ansible Ansible configuration options. For more information, see ansible properties . extraMounts The files to mount into an Ansible Execution Pod. hostName The node name. managementNetwork Name of the network to use for management (SSH/Ansible). networkData NetworkData configuration for the node. networks Instance networks. userData Node-specific user data. 5.5.3. ansible Defines the group of Ansible configuration options. Table 5.3. ansible properties Field Description ansibleUser The user associated with the secret you created in Creating the data plane secrets . Default: rhel-user ansibleHost SSH host for the Ansible connection. ansiblePort SSH port for the Ansible connection. ansibleVars The Ansible variables that customize the set of nodes. You can use this property to configure any custom Ansible variable, including the Ansible variables available for each edpm-ansible role. For a complete list of Ansible variables by role, see the edpm-ansible documentation . Note The ansibleVars parameters that you can configure for an OpenStackDataPlaneNodeSet CR are determined by the services defined for the OpenStackDataPlaneNodeSet . The OpenStackDataPlaneService CRs call the Ansible playbooks from the edpm-ansible playbook collection , which include the roles that are executed as part of the data plane service. ansibleVarsFrom A list of sources to populate Ansible variables from. Values defined by an AnsibleVars with a duplicate key take precedence. For more information, see ansibleVarsFrom properties . 5.5.4. ansibleVarsFrom Defines the list of sources to populate Ansible variables from. Table 5.4. ansibleVarsFrom properties Field Description prefix An optional identifier to prepend to each key in the ConfigMap . Must be a C_IDENTIFIER. configMapRef The ConfigMap CR to select the ansibleVars from. secretRef The Secret CR to select the ansibleVars from. 5.6. Deploying the data plane You use the OpenStackDataPlaneDeployment CRD to configure the services on the data plane nodes and deploy the data plane. You control the execution of Ansible on the data plane by creating OpenStackDataPlaneDeployment custom resources (CRs). Each OpenStackDataPlaneDeployment CR models a single Ansible execution. When the OpenStackDataPlaneDeployment successfully completes execution, it does not automatically execute the Ansible again, even if the OpenStackDataPlaneDeployment or related OpenStackDataPlaneNodeSet resources are changed. To start another Ansible execution, you must create another OpenStackDataPlaneDeployment CR. Create an OpenStackDataPlaneDeployment (CR) that deploys each of your OpenStackDataPlaneNodeSet CRs. Procedure Create a file on your workstation named openstack_data_plane_deploy.yaml to define the OpenStackDataPlaneDeployment CR: 1 The OpenStackDataPlaneDeployment CR name must be unique, must consist of lower case alphanumeric characters, - (hyphen) or . (period), and must start and end with an alphanumeric character. Update the name in this example to a name that reflects the node sets in the deployment. Add all the OpenStackDataPlaneNodeSet CRs that you want to deploy: Replace <nodeSet_name> with the names of the OpenStackDataPlaneNodeSet CRs that you want to include in your data plane deployment. Save the openstack_data_plane_deploy.yaml deployment file. Deploy the data plane: You can view the Ansible logs while the deployment executes: If the oc logs command returns an error similar to the following error, increase the --max-log-requests value: Verify that the data plane is deployed: For information about the meaning of the returned status, see Data plane conditions and states . If the status indicates that the data plane has not been deployed, then troubleshoot the deployment. For information, see Troubleshooting the data plane creation and deployment . Map the Compute nodes to the Compute cell that they are connected to: If you did not create additional cells, this command maps the Compute nodes to cell1 . Access the remote shell for the openstackclient pod and verify that the deployed Compute nodes are visible on the control plane: 5.7. Data plane conditions and states Each data plane resource has a series of conditions within their status subresource that indicates the overall state of the resource, including its deployment progress. For an OpenStackDataPlaneNodeSet , until an OpenStackDataPlaneDeployment has been started and finished successfully, the Ready condition is False . When the deployment succeeds, the Ready condition is set to True . A subsequent deployment sets the Ready condition to False until the deployment succeeds, when the Ready condition is set to True . Table 5.5. OpenStackDataPlaneNodeSet CR conditions Condition Description Ready "True": The OpenStackDataPlaneNodeSet CR is successfully deployed. "False": The deployment is not yet requested or has failed, or there are other failed conditions. SetupReady "True": All setup tasks for a resource are complete. Setup tasks include verifying the SSH key secret, verifying other fields on the resource, and creating the Ansible inventory for each resource. Each service-specific condition is set to "True" when that service completes deployment. You can check the service conditions to see which services have completed their deployment, or which services failed. DeploymentReady "True": The NodeSet has been successfully deployed. InputReady "True": The required inputs are available and ready. NodeSetDNSDataReady "True": DNSData resources are ready. NodeSetIPReservationReady "True": The IPSet resources are ready. NodeSetBaremetalProvisionReady "True": Bare-metal nodes are provisioned and ready. Table 5.6. OpenStackDataPlaneNodeSet status fields Status field Description Deployed "True": The OpenStackDataPlaneNodeSet CR is successfully deployed. "False": The deployment is not yet requested or has failed, or there are other failed conditions. DNSClusterAddresses CtlplaneSearchDomain Table 5.7. OpenStackDataPlaneDeployment CR conditions Condition Description Ready "True": The data plane is successfully deployed. "False": The data plane deployment failed, or there are other failed conditions. DeploymentReady "True": The data plane is successfully deployed. InputReady "True": The required inputs are available and ready. <NodeSet> Deployment Ready "True": The deployment has succeeded for the named NodeSet , indicating all services for the NodeSet have succeeded. <NodeSet> <Service> Deployment Ready "True": The deployment has succeeded for the named NodeSet and Service . Each <NodeSet> <Service> Deployment Ready specific condition is set to "True" as that service completes successfully for the named NodeSet . Once all services are complete for a NodeSet , the <NodeSet> Deployment Ready condition is set to "True". The service conditions indicate which services have completed their deployment, or which services failed and for which NodeSets . Table 5.8. OpenStackDataPlaneDeployment status fields Status field Description Deployed "True": The data plane is successfully deployed. All Services for all NodeSets have succeeded. "False": The deployment is not yet requested or has failed, or there are other failed conditions. Table 5.9. OpenStackDataPlaneService CR conditions Condition Description Ready "True": The service has been created and is ready for use. "False": The service has failed to be created. 5.8. Troubleshooting data plane creation and deployment To troubleshoot a deployment when services are not deploying or operating correctly, you can check the job condition message for the service, and you can check the logs for a node set. 5.8.1. Checking the job condition message for a service Each data plane deployment in the environment has associated services. Each of these services have a job condition message that matches the current status of the AnsibleEE job executing for that service. You can use this information to troubleshoot deployments when services are not deploying or operating correctly. Procedure Determine the name and status of all deployments: The following example output shows two deployments currently in progress: Retrieve and inspect Ansible execution jobs. The Kubernetes jobs are labelled with the name of the OpenStackDataPlaneDeployment . You can list jobs for each OpenStackDataPlaneDeployment by using the label: You can check logs by using oc logs -f job/<job-name> , for example, if you want to check the logs from the configure-network job: 5.8.1.1. Job condition messages AnsibleEE jobs have an associated condition message that indicates the current state of the service job. This condition message is displayed in the MESSAGE field of the oc get job <job_name> command output. Jobs return one of the following conditions when queried: Job not started : The job has not started. Job not found : The job could not be found. Job is running : The job is currently running. Job complete : The job execution is complete. Job error occurred <error_message> : The job stopped executing unexpectedly. The <error_message> is replaced with a specific error message. To further investigate a service that is displaying a particular job condition message, view its logs by using the command oc logs job/<service> . For example, to view the logs for the repo-setup-openstack-edpm service, use the command oc logs job/repo-setup-openstack-edpm . 5.8.2. Checking the logs for a node set You can access the logs for a node set to check for deployment issues. Procedure Retrieve pods with the OpenStackAnsibleEE label: SSH into the pod you want to check: Pod that is running: Pod that is not running: List the directories in the /runner/artifacts mount: View the stdout for the required artifact:

Commands:
ssh-keygen -f <key_file_name> -N "" -t rsa -b 4096
oc create secret generic dataplane-ansible-ssh-private-key-secret --save-config --dry-run=client --from-file=ssh-privatekey=<key_file_name> --from-file=ssh-publickey=<key_file_name>.pub [--from-file=authorized_keys=<key_file_name>.pub] -n openstack -o yaml | oc apply -f -
ssh-keygen -f ./nova-migration-ssh-key -t ecdsa-sha2-nistp521 -N ''
oc create secret generic nova-migration-ssh-key --save-config --from-file=ssh-privatekey=nova-migration-ssh-key --from-file=ssh-publickey=nova-migration-ssh-key.pub -n openstack -o yaml | oc apply -f -
apiVersion: v1 kind: Secret metadata: name: subscription-manager namespace: openstack data: username: <base64_username> password: <base64_password>
echo -n <string> | base64
oc create -f secret_subscription.yaml -n openstack
oc create secret generic redhat-registry --from-literal edpm_container_registry_logins='{"registry.redhat.io": {"<username>": "<password>"}}'
apiVersion: v1 kind: Secret metadata: name: libvirt-secret namespace: openstack type: Opaque data: LibvirtPassword: <base64_password>
echo -n <password> | base64
oc apply -f secret_libvirt.yaml -n openstack
oc describe secret dataplane-ansible-ssh-private-key-secret oc describe secret nova-migration-ssh-key oc describe secret subscription-manager oc describe secret redhat-registry oc describe secret libvirt-secret
apiVersion: dataplane.openstack.org/v1beta1 kind: OpenStackDataPlaneNodeSet metadata: name: openstack-data-plane 1 namespace: openstack spec: env: 2 - name: ANSIBLE_FORCE_COLOR value: "True"
spec: networkAttachments: - ctlplane
preProvisioned: true
nodeTemplate: ansibleSSHPrivateKeySecret: <secret-key>
nodeTemplate: extraMounts: - extraVolType: Logs volumes: - name: ansible-logs persistentVolumeClaim: claimName: <pvc_name> mounts: - name: ansible-logs mountPath: "/runner/artifacts"
nodeTemplate: managementNetwork: ctlplane
nodeTemplate: ansible: ansibleUser: cloud-admin 1 ansiblePort: 22 ansibleVarsFrom: - prefix: subscription_manager_ secretRef: name: subscription-manager - secretRef: name: redhat-registry ansibleVars: 2 edpm_bootstrap_command: | subscription-manager register --username {{ subscription_manager_username }} --password {{ subscription_manager_password }} subscription-manager attach --pool=<pool_id> 3 subscription-manager release --set=9.4 subscription-manager repos --disable=* subscription-manager repos --enable=rhel-9-for-x86_64-baseos-eus-rpms --enable=rhel-9-for-x86_64-appstream-eus-rpms --enable=rhel-9-for-x86_64-highavailability-eus-rpms --enable=fast-datapath-for-rhel-9-x86_64-rpms --enable=rhoso-18.0-for-rhel-9-x86_64-rpms --enable=rhceph-7-tools-for-rhel-9-x86_64-rpms edpm_bootstrap_release_version_package: []
nodeTemplate: ansible: ansibleVars: edpm_network_config_os_net_config_mappings: edpm-compute-0: nic1: 52:54:04:60:55:22 1 neutron_physical_bridge_name: br-ex neutron_public_interface_name: eth0 edpm_network_config_update: false 2 edpm_network_config_template: | --- {% set mtu_list = [ctlplane_mtu] %} {% for network in nodeset_networks %} {{ mtu_list.append(lookup('vars', networks_lower[network] ~ '_mtu')) }} {%- endfor %} {% set min_viable_mtu = mtu_list | max %} network_config: - type: ovs_bridge name: {{ neutron_physical_bridge_name }} mtu: {{ min_viable_mtu }} use_dhcp: false dns_servers: {{ ctlplane_dns_nameservers }} domain: {{ dns_search_domains }} addresses: - ip_netmask: {{ ctlplane_ip }}/{{ ctlplane_cidr }} routes: {{ ctlplane_host_routes }} members: - type: interface name: nic1 mtu: {{ min_viable_mtu }} # force the MAC address of the bridge to this interface primary: true {% for network in nodeset_networks %} - type: vlan mtu: {{ lookup('vars', networks_lower[network] ~ '_mtu') }} vlan_id: {{ lookup('vars', networks_lower[network] ~ '_vlan_id') }} addresses: - ip_netmask: {{ lookup('vars', networks_lower[network] ~ '_ip') }}/{{ lookup('vars', networks_lower[network] ~ '_cidr') }} routes: {{ lookup('vars', networks_lower[network] ~ '_host_routes') }} {% endfor %}
nodes: edpm-compute-0: 1 hostName: edpm-compute-0 networks: 2 - name: ctlplane subnetName: subnet1 defaultRoute: true fixedIP: 192.168.122.100 3 - name: internalapi subnetName: subnet1 fixedIP: 172.17.0.100 - name: storage subnetName: subnet1 fixedIP: 172.18.0.100 - name: tenant subnetName: subnet1 fixedIP: 172.19.0.100 ansible: ansibleHost: 192.168.122.100 ansibleUser: cloud-admin ansibleVars: 4 fqdn_internal_api: edpm-compute-0.example.com edpm-compute-1: hostName: edpm-compute-1 networks: - name: ctlplane subnetName: subnet1 defaultRoute: true fixedIP: 192.168.122.101 - name: internalapi subnetName: subnet1 fixedIP: 172.17.0.101 - name: storage subnetName: subnet1 fixedIP: 172.18.0.101 - name: tenant subnetName: subnet1 fixedIP: 172.19.0.101 ansible: ansibleHost: 192.168.122.101 ansibleUser: cloud-admin ansibleVars: fqdn_internal_api: edpm-compute-1.example.com
oc create --save-config -f openstack_preprovisioned_node_set.yaml -n openstack
oc wait openstackdataplanenodeset openstack-data-plane --for condition=SetupReady --timeout=10m
oc get secret | grep openstack-data-plane dataplanenodeset-openstack-data-plane Opaque 1 3m50s
oc get openstackdataplaneservice -n openstack NAME AGE bootstrap 46m ceph-client 46m ceph-hci-pre 46m configure-network 46m configure-os 46m
apiVersion: dataplane.openstack.org/v1beta1 kind: OpenStackDataPlaneNodeSet metadata: name: openstack-data-plane namespace: openstack spec: env: - name: ANSIBLE_FORCE_COLOR value: "True" networkAttachments: - ctlplane preProvisioned: true nodeTemplate: ansibleSSHPrivateKeySecret: dataplane-ansible-ssh-private-key-secret extraMounts: - extraVolType: Logs volumes: - name: ansible-logs persistentVolumeClaim: claimName: <pvc_name> mounts: - name: ansible-logs mountPath: "/runner/artifacts" managementNetwork: ctlplane ansible: ansibleUser: cloud-admin ansiblePort: 22 ansibleVarsFrom: - prefix: subscription_manager_ secretRef: name: subscription-manager - secretRef: name: redhat-registry ansibleVars: edpm_bootstrap_command: | subscription-manager register --username {{ subscription_manager_username }} --password {{ subscription_manager_password }} subscription-manager release --set=9.4 subscription-manager repos --disable=* subscription-manager repos --enable=rhel-9-for-x86_64-baseos-eus-rpms --enable=rhel-9-for-x86_64-appstream-eus-rpms --enable=rhel-9-for-x86_64-highavailability-eus-rpms --enable=fast-datapath-for-rhel-9-x86_64-rpms --enable=rhoso-18.0-for-rhel-9-x86_64-rpms --enable=rhceph-7-tools-for-rhel-9-x86_64-rpms edpm_bootstrap_release_version_package: [] edpm_network_config_os_net_config_mappings: edpm-compute-0: nic1: 52:54:04:60:55:22 neutron_physical_bridge_name: br-ex neutron_public_interface_name: eth0 edpm_network_config_template: | --- {% set mtu_list = [ctlplane_mtu] %} {% for network in nodeset_networks %} {{ mtu_list.append(lookup('vars', networks_lower[network] ~ '_mtu')) }} {%- endfor %} {% set min_viable_mtu = mtu_list | max %} network_config: - type: ovs_bridge name: {{ neutron_physical_bridge_name }} mtu: {{ min_viable_mtu }} use_dhcp: false dns_servers: {{ ctlplane_dns_nameservers }} domain: {{ dns_search_domains }} addresses: - ip_netmask: {{ ctlplane_ip }}/{{ ctlplane_cidr }} routes: {{ ctlplane_host_routes }} members: - type: interface name: nic1 mtu: {{ min_viable_mtu }} # force the MAC address of the bridge to this interface primary: true {% for network in nodeset_networks %} - type: vlan mtu: {{ lookup('vars', networks_lower[network] ~ '_mtu') }} vlan_id: {{ lookup('vars', networks_lower[network] ~ '_vlan_id') }} addresses: - ip_netmask: {{ lookup('vars', networks_lower[network] ~ '_ip') }}/{{ lookup('vars', networks_lower[network] ~ '_cidr') }} routes: {{ lookup('vars', networks_lower[network] ~ '_host_routes') }} {% endfor %} nodes: edpm-compute-0: hostName: edpm-compute-0 networks: - name: ctlplane subnetName: subnet1 defaultRoute: true fixedIP: 192.168.122.100 - name: internalapi subnetName: subnet1 fixedIP: 172.17.0.100 - name: storage subnetName: subnet1 fixedIP: 172.18.0.100 - name: tenant subnetName: subnet1 fixedIP: 172.19.0.100 ansible: ansibleHost: 192.168.122.100 ansibleUser: cloud-admin ansibleVars: fqdn_internal_api: edpm-compute-0.example.com edpm-compute-1: hostName: edpm-compute-1 networks: - name: ctlplane subnetName: subnet1 defaultRoute: true fixedIP: 192.168.122.101 - name: internalapi subnetName: subnet1 fixedIP: 172.17.0.101 - name: storage subnetName: subnet1 fixedIP: 172.18.0.101 - name: tenant subnetName: subnet1 fixedIP: 172.19.0.101 ansible: ansibleHost: 192.168.122.101 ansibleUser: cloud-admin ansibleVars: fqdn_internal_api: edpm-compute-1.example.com
oc patch provisioning provisioning-configuration --type merge -p '{"spec":{"watchAllNamespaces": true }}'
oc patch provisioning provisioning-configuration --type merge -p '{"spec":{"virtualMediaViaExternalNetwork": true }}'
apiVersion: v1 kind: Secret metadata: name: edpm-compute-0-bmc-secret namespace: openstack type: Opaque data: username: <base64_username> password: <base64_password>
echo -n <string> | base64
apiVersion: metal3.io/v1alpha1 kind: BareMetalHost metadata: name: edpm-compute-0 namespace: openstack labels: app: openstack workload: compute spec: bmc: address: redfish-virtualmedia+http://192.168.111.1:8000/redfish/v1/Systems/e8efd888-f844-4fe0-9e2e-498f4ab7806d 1 credentialsName: edpm-compute-0-bmc-secret 2 bootMACAddress: 00:c7:e4:a7:e7:f3 bootMode: UEFI online: false [preprovisioningNetworkDataName: <network_config_secret_name>] 3
oc create -f bmh_nodes.yaml
oc get bmh NAME STATE CONSUMER ONLINE ERROR AGE edpm-compute-0 Available openstack-edpm true 2d21h edpm-compute-1 Available openstack-edpm true 2d21h
apiVersion: dataplane.openstack.org/v1beta1 kind: OpenStackDataPlaneNodeSet metadata: name: openstack-data-plane 1 namespace: openstack spec: tlsEnabled: true env: 2 - name: ANSIBLE_FORCE_COLOR value: "True"
spec: networkAttachments: - ctlplane
preProvisioned: false
baremetalSetTemplate: deploymentSSHSecret: dataplane-ansible-ssh-private-key-secret bmhNamespace: <bmh_namespace> cloudUserName: <ansible_ssh_user> bmhLabelSelector: app: <bmh_label> ctlplaneInterface: <interface> dnsSearchDomains: - osptest.openstack.org
baremetalSetTemplate: provisionServerName: my-os-provision-server
nodeTemplate: ansibleSSHPrivateKeySecret: <secret-key>
nodeTemplate: extraMounts: - extraVolType: Logs volumes: - name: ansible-logs persistentVolumeClaim: claimName: <pvc_name> mounts: - name: ansible-logs mountPath: "/runner/artifacts"
nodeTemplate: managementNetwork: ctlplane
nodeTemplate: ansible: ansibleUser: cloud-admin 1 ansiblePort: 22 ansibleVarsFrom: - prefix: subscription_manager_ secretRef: name: subscription-manager - secretRef: name: redhat-registry ansibleVars: 2 edpm_bootstrap_command: | subscription-manager register --username {{ subscription_manager_username }} --password {{ subscription_manager_password }} subscription-manager attach --pool=<pool_id> 3 subscription-manager release --set=9.4 subscription-manager repos --disable=* subscription-manager repos --enable=rhel-9-for-x86_64-baseos-eus-rpms --enable=rhel-9-for-x86_64-appstream-eus-rpms --enable=rhel-9-for-x86_64-highavailability-eus-rpms --enable=fast-datapath-for-rhel-9-x86_64-rpms --enable=rhoso-18.0-for-rhel-9-x86_64-rpms --enable=rhceph-7-tools-for-rhel-9-x86_64-rpms edpm_bootstrap_release_version_package: []
nodeTemplate: ansible: ansibleVars: edpm_network_config_os_net_config_mappings: edpm-compute-0: nic1: 52:54:04:60:55:22 1 edpm-compute-1: nic1: 52:54:04:60:55:22 neutron_physical_bridge_name: br-ex neutron_public_interface_name: eth0 edpm_network_config_update: false 2 edpm_network_config_template: | --- {% set mtu_list = [ctlplane_mtu] %} {% for network in nodeset_networks %} {{ mtu_list.append(lookup('vars', networks_lower[network] ~ '_mtu')) }} {%- endfor %} {% set min_viable_mtu = mtu_list | max %} network_config: - type: ovs_bridge name: {{ neutron_physical_bridge_name }} mtu: {{ min_viable_mtu }} use_dhcp: false dns_servers: {{ ctlplane_dns_nameservers }} domain: {{ dns_search_domains }} addresses: - ip_netmask: {{ ctlplane_ip }}/{{ ctlplane_cidr }} routes: {{ ctlplane_host_routes }} members: - type: interface name: nic1 mtu: {{ min_viable_mtu }} # force the MAC address of the bridge to this interface primary: true {% for network in nodeset_networks %} - type: vlan mtu: {{ lookup('vars', networks_lower[network] ~ '_mtu') }} vlan_id: {{ lookup('vars', networks_lower[network] ~ '_vlan_id') }} addresses: - ip_netmask: {{ lookup('vars', networks_lower[network] ~ '_ip') }}/{{ lookup('vars', networks_lower[network] ~ '_cidr') }} routes: {{ lookup('vars', networks_lower[network] ~ '_host_routes') }} {% endfor %}
nodes: edpm-compute-0: 1 hostName: edpm-compute-0 networks: 2 - name: ctlplane subnetName: subnet1 defaultRoute: true fixedIP: 192.168.122.100 3 - name: internalapi subnetName: subnet1 - name: storage subnetName: subnet1 - name: tenant subnetName: subnet1 networkData: 4 name: edpm-compute-0-network-data namespace: openstack userData: 5 name: edpm-compute-0-user-data namespace: openstack ansible: ansibleHost: 192.168.122.100 ansibleUser: cloud-admin ansibleVars: 6 fqdn_internal_api: edpm-compute-0.example.com bmhLabelSelector: 7 nodeName: edpm-compute-0 edpm-compute-1: hostName: edpm-compute-1 networks: - name: ctlplane subnetName: subnet1 defaultRoute: true fixedIP: 192.168.122.101 - name: internalapi subnetName: subnet1 - name: storage subnetName: subnet1 - name: tenant subnetName: subnet1 networkData: name: edpm-compute-1-network-data namespace: openstack userData: name: edpm-compute-1-user-data namespace: openstack ansible: ansibleHost: 192.168.122.101 ansibleUser: cloud-admin ansibleVars: fqdn_internal_api: edpm-compute-1.example.com bmhLabelSelector: nodeName: edpm-compute-1
oc create --save-config -f openstack_unprovisioned_node_set.yaml -n openstack
oc wait openstackdataplanenodeset openstack-data-plane --for condition=SetupReady --timeout=10m
oc get secret -n openstack | grep openstack-data-plane dataplanenodeset-openstack-data-plane Opaque 1 3m50s
oc get bmh NAME STATE CONSUMER ONLINE ERROR AGE edpm-compute-0 provisioned openstack-data-plane true 3d21h
oc get openstackdataplaneservice -n openstack NAME AGE bootstrap 8m40s ceph-client 8m40s ceph-hci-pre 8m40s configure-network 8m40s configure-os 8m40s
apiVersion: dataplane.openstack.org/v1beta1 kind: OpenStackDataPlaneNodeSet metadata: name: openstack-data-plane namespace: openstack spec: env: - name: ANSIBLE_FORCE_COLOR value: "True" networkAttachments: - ctlplane preProvisioned: false baremetalSetTemplate: deploymentSSHSecret: dataplane-ansible-ssh-private-key-secret bmhNamespace: openshift-machine-api cloudUserName: cloud-admin bmhLabelSelector: app: openstack ctlplaneInterface: enp1s0 dnsSearchDomains: - osptest.openstack.org nodeTemplate: ansibleSSHPrivateKeySecret: dataplane-ansible-ssh-private-key-secret extraMounts: - extraVolType: Logs volumes: - name: ansible-logs persistentVolumeClaim: claimName: <pvc_name> mounts: - name: ansible-logs mountPath: "/runner/artifacts" managementNetwork: ctlplane ansible: ansibleUser: cloud-admin ansiblePort: 22 ansibleVarsFrom: - prefix: subscription_manager_ secretRef: name: subscription-manager - secretRef: name: redhat-registry ansibleVars: edpm_bootstrap_command: | subscription-manager register --username {{ subscription_manager_username }} --password {{ subscription_manager_password }} subscription-manager release --set=9.4 subscription-manager repos --disable=* subscription-manager repos --enable=rhel-9-for-x86_64-baseos-eus-rpms --enable=rhel-9-for-x86_64-appstream-eus-rpms --enable=rhel-9-for-x86_64-highavailability-eus-rpms --enable=fast-datapath-for-rhel-9-x86_64-rpms --enable=rhoso-18.0-for-rhel-9-x86_64-rpms --enable=rhceph-7-tools-for-rhel-9-x86_64-rpms edpm_bootstrap_release_version_package: [] edpm_network_config_os_net_config_mappings: edpm-compute-0: nic1: 52:54:04:60:55:22 edpm-compute-1: nic1: 52:54:04:60:55:22 neutron_physical_bridge_name: br-ex neutron_public_interface_name: eth0 edpm_network_config_template: | --- {% set mtu_list = [ctlplane_mtu] %} {% for network in nodeset_networks %} {{ mtu_list.append(lookup('vars', networks_lower[network] ~ '_mtu')) }} {%- endfor %} {% set min_viable_mtu = mtu_list | max %} network_config: - type: ovs_bridge name: {{ neutron_physical_bridge_name }} mtu: {{ min_viable_mtu }} use_dhcp: false dns_servers: {{ ctlplane_dns_nameservers }} domain: {{ dns_search_domains }} addresses: - ip_netmask: {{ ctlplane_ip }}/{{ ctlplane_cidr }} routes: {{ ctlplane_host_routes }} members: - type: interface name: nic1 mtu: {{ min_viable_mtu }} # force the MAC address of the bridge to this interface primary: true {% for network in nodeset_networks %} - type: vlan mtu: {{ lookup('vars', networks_lower[network] ~ '_mtu') }} vlan_id: {{ lookup('vars', networks_lower[network] ~ '_vlan_id') }} addresses: - ip_netmask: {{ lookup('vars', networks_lower[network] ~ '_ip') }}/{{ lookup('vars', networks_lower[network] ~ '_cidr') }} routes: {{ lookup('vars', networks_lower[network] ~ '_host_routes') }} {% endfor %} nodes: edpm-compute-0: hostName: edpm-compute-0 networks: - name: ctlplane subnetName: subnet1 defaultRoute: true fixedIP: 192.168.122.100 - name: internalapi subnetName: subnet1 - name: storage subnetName: subnet1 - name: tenant subnetName: subnet1 ansible: ansibleHost: 192.168.122.100 ansibleUser: cloud-admin ansibleVars: fqdn_internal_api: edpm-compute-0.example.com bmhLabelSelector: nodeName: edpm-compute-0 edpm-compute-1: hostName: edpm-compute-1 networks: - name: ctlplane subnetName: subnet1 defaultRoute: true fixedIP: 192.168.122.101 - name: internalapi subnetName: subnet1 - name: storage subnetName: subnet1 - name: tenant subnetName: subnet1 ansible: ansibleHost: 192.168.122.101 ansibleUser: cloud-admin ansibleVars: fqdn_internal_api: edpm-compute-1.example.com bmhLabelSelector: nodeName: edpm-compute-1
apiVersion: dataplane.openstack.org/v1beta1 kind: OpenStackDataPlaneDeployment metadata: name: data-plane-deploy 1 namespace: openstack
spec: nodeSets: - openstack-data-plane - <nodeSet_name> - - <nodeSet_name>
oc create -f openstack_data_plane_deploy.yaml -n openstack
oc get pod -l app=openstackansibleee -w oc logs -l app=openstackansibleee -f --max-log-requests 10
error: you are attempting to follow 19 log streams, but maximum allowed concurrency is 10, use --max-log-requests to increase the limit
oc get openstackdataplanedeployment -n openstack NAME STATUS MESSAGE data-plane-deploy True Setup Complete oc get openstackdataplanenodeset -n openstack NAME STATUS MESSAGE openstack-data-plane True NodeSet Ready
oc rsh nova-cell0-conductor-0 nova-manage cell_v2 discover_hosts --verbose
oc rsh -n openstack openstackclient openstack hypervisor list
oc get openstackdataplanedeployment
oc get openstackdataplanedeployment NAME NODESETS STATUS MESSAGE edpm-compute ["openstack-edpm-ipam"] False Deployment in progress
oc get job -l openstackdataplanedeployment=edpm-compute NAME STATUS COMPLETIONS DURATION AGE bootstrap-edpm-compute-openstack-edpm-ipam Complete 1/1 78s 25h configure-network-edpm-compute-openstack-edpm-ipam Complete 1/1 37s 25h configure-os-edpm-compute-openstack-edpm-ipam Complete 1/1 66s 25h download-cache-edpm-compute-openstack-edpm-ipam Complete 1/1 64s 25h install-certs-edpm-compute-openstack-edpm-ipam Complete 1/1 46s 25h install-os-edpm-compute-openstack-edpm-ipam Complete 1/1 57s 25h libvirt-edpm-compute-openstack-edpm-ipam Complete 1/1 2m37s 25h neutron-metadata-edpm-compute-openstack-edpm-ipam Complete 1/1 61s 25h nova-edpm-compute-openstack-edpm-ipam Complete 1/1 3m20s 25h ovn-edpm-compute-openstack-edpm-ipam Complete 1/1 78s 25h run-os-edpm-compute-openstack-edpm-ipam Complete 1/1 33s 25h ssh-known-hosts-edpm-compute Complete 1/1 19s 25h telemetry-edpm-compute-openstack-edpm-ipam Complete 1/1 2m5s 25h validate-network-edpm-compute-openstack-edpm-ipam Complete 1/1 16s 25h
oc logs -f jobs/configure-network-edpm-compute-openstack-edpm-ipam | tail -n2 PLAY RECAP ********************************************************************* edpm-compute-0 : ok=22 changed=0 unreachable=0 failed=0 skipped=17 rescued=0 ignored=0
oc get pods -l app=openstackansibleee configure-network-edpm-compute-j6r4l 0/1 Completed 0 3m36s validate-network-edpm-compute-6g7n9 0/1 Pending 0 0s validate-network-edpm-compute-6g7n9 0/1 ContainerCreating 0 11s validate-network-edpm-compute-6g7n9 1/1 Running 0 13s
oc rsh validate-network-edpm-compute-6g7n9
oc debug configure-network-edpm-compute-j6r4l
ls /runner/artifacts configure-network-edpm-compute validate-network-edpm-compute
cat /runner/artifacts/configure-network-edpm-compute/stdout