Deployment of RHOCP VIM components

Two methods are available to deploy the RHOCP VIM components.

  • Using the nps autodeploy CLI command.

  • Manually installing and configuring RHOCP.

Hewlett Packard Enterprise recommends usage of nps autodeploy CLI command for deployment of RHOCP VIM components.

The nps autodeploy is a CLI wrapper command to automatically deploy OCP cluster end-to-end. The CLI wrapper:
  • Deploys bootstrap, master, and worker nodes, and ensures that the cluster is ready for launching workloads.

  • Deploys HPE Nimble CSI driver for Kubernetes and configures Persistent Volume for Image Registry.

  • Configures SR-IOV on worker nodes.

A state machine is maintained to control the flow. You can view the status of the state machine using the nps show --data vim CLI command.

Initially when nps autodeploy is started the VIM state is NA and as the nps autodeploy completes successfully the VIM state changes to OCP_CLUSTER_CONFIGURED.

The following sequence is performed for deploying RHOCP using nps autodeploy.

  1. Create ignition files.

    The OCP cluster uses the ignition files to start the installation.

    Ensure to complete the cluster installation within 24 hours as the generated Ignition files contain certificates that expire after 24 hours.

  2. Deploy bootstrap node.

    Bootstrap node is required to bring up the master nodes.

  3. Deploy master node.

    Master nodes are required to bring up the worker nodes.

  4. Replace bootstrap hostname entry manually in both Load Balancers and DNS with worker node.

  5. Deploy RHCOS worker nodes.

    • Worker nodes that host the workload are deployed.

    • As part of RHCOS worker node deployment, two RHCOS worker nodes are deployed.

      • One worker node is deployed on the server with os_type as rhcos in the data model.

      • Second worker node is deployed by reconfiguring bootstrap node as RHCOS worker node.

  6. Approve CSR for RHCOS worker nodes and check for master cluster completion.

  7. Configure HPE Nimble CSI driver for Kubernetes.

  8. Configure storage for image registry.

  9. Configure OLM, if the deployment mode is restricted (offline).

  10. Configure SR-IOV on worker nodes.