Chapter 21. Configuring for VMware vSphere

1. Create a VM folder and move OpenShift Container Platform Node VMs to this folder.

2. Verify that the Node VM names complies with the regex [a-z](()?[0-9a-z])?(\.[a-z0-9](([-0-9a-z])?[0-9a-z])?)*.

   Important

   VM Names can not:

   • begin with numbers.
   • have any capital letters.
   • have any special characters except -.
   • be shorter than three characters and longer than 63 characters.

3. Set the disk.EnableUUID parameter to TRUE for each Node VM. This ensures that the VMDK always presents a consistent UUID to the VM, allowing the disk to be mounted properly. For every virtual machine node that will be participating in the cluster, follow the steps below using the GOVC tool:

   1. Set up the GOVC environment:

      export GOVC_URL='vCenter IP OR FQDN'
      export GOVC_USERNAME='vCenter User'
      export GOVC_PASSWORD='vCenter Password'
      export GOVC_INSECURE=1

   2. Find the Node VM paths:

      govc ls /datacenter/vm/<vm-folder-name>

   3. Set disk.EnableUUID to true for all VMs:

      govc vm.change -e="disk.enableUUID=1" -vm='VM Path'

      Note

      If OpenShift Container Platform node VMs are created from a template VM, then disk.EnableUUID=1 can be set on the template VM. VMs cloned from this template, inherit this property.

4. Create and assign roles to the vSphere Cloud Provider user and vSphere entities. vSphere Cloud Provider requires the following privileges to interact with vCenter. See the vSphere Documentation Center for steps to create a custom role, user and role assignment.

   Roles	Privileges	Entities	Propagate to Children
   manage-k8s-node-vms	Resource.AssignVMToPool System.Anonymous System.Read System.View VirtualMachine.Config.AddExistingDisk VirtualMachine.Config.AddNewDisk VirtualMachine.Config.AddRemoveDevice VirtualMachine.Config.RemoveDisk VirtualMachine.Inventory.Create VirtualMachine.Inventory.Delete	Cluster, Hosts, VM Folder	Yes
   manage-k8s-volumes	Datastore.AllocateSpace Datastore.FileManagement System.Anonymous System.Read System.View	Datastore	No
   k8s-system-read-and-spbm-profile-view	StorageProfile.View System.Anonymous System.Read System.View	vCenter	No
   ReadOnly	System.Anonymous System.Read System.View	Datacenter, Datastore Cluster, Datastore Storage Folder	No

Procedure

1. Add the following section to the Ansible inventory file:

   [OSEv3:vars]
   openshift_cloudprovider_kind=vsphere
   openshift_cloudprovider_vsphere_username=administrator@vsphere.local 1
   openshift_cloudprovider_vsphere_password=<password>
   openshift_cloudprovider_vsphere_host=10.x.y.32 2
   openshift_cloudprovider_vsphere_datacenter=<Datacenter> 3
   openshift_cloudprovider_vsphere_datastore=<Datastore> 4

   1

   The user name with the appropriate permissions to create and attach disks in vSphere.

   2

   The vCenter server address.

   3

   The vCenter Datacenter name where the OpenShift Container Platform VMs are located.

   4

   The datastore used for creating VMDKs.

1. Edit or create the node configuration file on all nodes (/etc/origin/node/node-config.yaml by default) and update the contents of the kubeletArguments section:

   kubeletArguments:
     cloud-provider:
       - "vsphere"
     cloud-config:
       - "/etc/origin/cloudprovider/vsphere.conf"

   Important

   When triggering a containerized installation, only the /etc/origin and /var/lib/origin directories are mounted to the master and node container. Therefore, node-config.yaml must be in /etc/origin/node rather than /etc/.

1. Log in to the CLI as a cluster administrator.

2. Check and back up existing node labels:

   $ oc describe node <node_name> | grep -Poz '(?s)Labels.*\n.*(?=Taints)'

3. Delete the nodes:

   $ oc delete node <node_name>

4. On each node host, restart the OpenShift Container Platform service.

   # systemctl restart atomic-openshift-node

5. Add back any labels on each node that you previously had.

1. Stop the application using the PV.
2. Clone the persistent disk.
3. Restart the application.
4. Create a backup of the cloned disk.
5. Delete the cloned disk.