Managing Virtual Machines with Red Hat OpenShift Virtualization

Instructions

1. From a terminal on the workstation machine, use the oc command to log in to your Red Hat OpenShift cluster as admin with redhatocp as the password.

   Cluster API endpoint

   https://api.ocp4.example.com:6443

   Web console URL

   https://console-openshift-console.apps.ocp4.example.com

   Open a web browser and log in to the OpenShift web console. Confirm that the two VMs are running under the storage-review project.

   1. From a terminal, log in to your OpenShift cluster as the admin user.

      [student@workstation ~]$ oc login -u admin -p redhatocp \
        https://api.ocp4.example.com:6443
      Login Successful
      ...output omitted...

   2. Switch to the storage-review project.

      [student@workstation ~]$ oc project storage-review
      Now using project "storage-review" on server "https://api.ocp4.example.com:6443".

   3. Identify the URL for the OpenShift web console.

      [student@workstation ~]$ oc whoami --show-console
      https://console-openshift-console.apps.ocp4.example.com

   4. Open a web browser and navigate to the web console URL. Select htpasswd_provider and log in as the admin user with redhatocp as the password when prompted.

   5. Navigate to Virtualization → VirtualMachines and then select the storage-review project. Confirm that the vm1 and vm2 VMs are running.

   Hide Solution

2. A disk named webroot is connected to the vm1 VM. Detach the disk and then connect it to the vm2 VM. Use the VirtIO interface when you connect the disk to the VM. Ensure that you preserve the data when you detach the disk.

   Ensure that the vm1 VM is running after you complete your work.

   To verify the disk, log in to the console of the vm2 VM as root with redhat as the password, and then run the lsblk command. The command output should list the new vdb disk.

   1. Use the OpenShift web console to stop the vm1 VM. Select the vm1 VM and then click Actions → Stop. Click Stop to confirm the operation, if needed. Wait for the machine to stop.

   2. Navigate to the Configuration → Disks tab. At the end of the row of the webroot disk, click the vertical ellipsis icon ⋮ and then click Detach. Click Detach to confirm.

   3. Click Actions → Start to start the VM.

   4. Navigate to Virtualization → VirtualMachines, select the vm2 VM, and then click Actions → Stop. Click Stop to confirm the operation, if needed. Wait for the machine to stop.

   5. Navigate to the Configuration → Disks tab and then click Add disk. Complete the form by using the following information and click Save confirm.

      Note

      If the Interface field is set to SCSI and VirtIO is not available, then click Cancel and start over. The web interface takes a few seconds to detect that the VM is stopped.

      Field	Value
      Use this disk as a boot source	Unset
      Name	webroot
      Source	Use an existing PVC
      PVC project	storage-review
      PVC name	webroot
      Type	Disk
      Interface	VirtIO

   6. Click Actions → Start to start the VM.

   7. Log in to the VM console and confirm that a new 1 GiB device is available.

      Navigate to the Console tab and then log in as the root user with redhat as the password. Run the lsblk command to list the block devices. Notice the 1 GiB vdb block device.

      [root@vm2 ~]# lsblk
      NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
      vda    252:0    0   10G  0 disk
      ├─vda1 252:1    0    1M  0 part
      ├─vda2 252:2    0  100M  0 part /boot/efi
      └─vda3 252:3    0  9.9G  0 part /
      vdb    252:16   0    1G  0 disk	

      The vdb device corresponds to the webroot disk.

   8. Log out of the VM console.

      [root@vm2 ~]# logout

   Hide Solution

3. Create the PV resource named nfs-pv, which declares an external NFS share. Ensure that you reserve the PV for a PVC named weblog in the storage-review namespace. You create the weblog PVC in a following step.

   The lab command prepared the ~/DO316/labs/storage-review/nfspv.yaml resource file that you can use as a model. To use that file, you must adapt it to the requirements.

   1. From the terminal on the workstation machine, edit the ~/DO316/labs/storage-review/nfspv.yaml resource file.

      apiVersion: v1
      kind: PersistentVolume
      metadata:
        name: nfs-pv
      spec:
        capacity:
          storage: 5Gi
        accessModes:
          - ReadWriteMany
        volumeMode: Filesystem
        claimRef:
          name: weblog
          namespace: storage-review
        nfs:
          path: /exports-ocp4/storage-review
          server: 192.168.50.254

   2. Use the oc command to create the resource:

      [student@workstation ~]$ oc apply -f ~/DO316/labs/storage-review/nfspv.yaml
      persistentvolume/nfs-pv created

      From the OpenShift web console, navigate to Storage → PersistentVolumes, click Create PersistentVolume, and then copy and paste the resource file into the YAML editor. Click Create to create the resource.

   3. Run the oc get pv command to verify your work.

      [student@workstation ~]$ oc get pv nfs-pv
      NAME    CAPACITY  ACCESS MODES  RECLAIM POLICY  STATUS     CLAIM                 …
      nfs-pv  5Gi       RWX           Retain          Available  storage-review/weblog …

   Hide Solution

4. Create the weblog PVC in the storage-review namespace with the following parameters:

   Field	Value
   PVC name	weblog
   Access mode	ReadWriteMany (RWX)
   Size	5 GiB
   Volume mode	Filesystem

   The lab command prepared the ~/DO316/labs/storage-review/nfspvc.yaml resource file that you can use as a model. To use that file, you must adapt it to the requirements.

   Confirm that Kubernetes binds the weblog PVC to the PV named nfs-pv.

   1. From the terminal, edit the ~/DO316/labs/storage-review/nfspvc.yaml resource file.

      apiVersion: v1
      kind: PersistentVolumeClaim
      metadata:
        name: weblog
        namespace: storage-review
      spec:
        resources:
          requests:
            storage: 5Gi
        accessModes:
          - ReadWriteMany
        volumeMode: Filesystem

   2. Use the oc command to create the resource:

      [student@workstation ~]$ oc apply -f ~/DO316/labs/storage-review/nfspvc.yaml
      persistentvolumeclaim/weblog created

      Note

      From the OpenShift web console, navigate to Storage → PersistentVolumeClaims, select the storage-review project, and click Create PersistentVolumeClaim → With Form. Complete the form by using the following information, and click Create to create the resource.

      Field	Value
      StorageClass	nfs-storage
      PersistentVolumeClaim name	weblog
      Access mode	Shared access (RWX)
      Size	5 GiB
      Use label selectors to request storage	Unset
      Volume mode	Filesystem

   3. Run the oc get pvc command to confirm that Kubernetes binds your PVC to the nfs-pv persistent volume.

      [student@workstation ~]$ oc get pvc weblog
      NAME     STATUS   VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
      weblog   Bound    nfs-pv   5Gi        RWX            nfs-storage    1m

   Hide Solution

5. Attach the weblog PVC as a disk to the vm2 VM by using a VirtIO interface.

   Ensure that the vm2 VM is running after you have completed your work.

   To verify the disk, log in to the console of the vm2 VM as root with redhat as the password, and then run the lsblk command. The command output should list a new 5 GiB disk named vdc.

   1. Use the OpenShift web console to stop the vm2 VM. Navigate to Virtualization → VirtualMachines, select the vm2 VM, and then click Actions → Stop. Click Stop to confirm the operation, if needed. Wait for the machine to stop.

   2. Navigate to the Configuration → Disks tab and then click Add disk. Complete the form by using the following information and click Save to confirm.

      Note

      If the Interface field is set to SCSI and VirtIO is not available, then click Cancel and start over. The web interface takes a few seconds to detect that the VM is stopped.

      Field	Value
      Use this disk as a boot source	Unset
      Name	weblog
      Source	Use an existing PVC
      PVC project	storage-review
      PVC name	weblog
      Type	Disk
      Interface	VirtIO

   3. Click Actions → Start to start the VM and wait until it finishes booting.

   4. Log in to the VM console and confirm that a new 5 GiB device is available.

      Navigate to the Console tab and then log in as the root user with redhat as the password. Run the lsblk command to list the block devices. Notice the 5 GiB vdc block device.

      [root@vm2 ~]# lsblk
      NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
      vda    252:0    0   10G  0 disk
      ├─vda1 252:1    0    1M  0 part
      ├─vda2 252:2    0  100M  0 part /boot/efi
      └─vda3 252:3    0  9.9G  0 part /
      vdb    252:16   0    1G  0 disk
      vdc    252:32   0    5G  0 disk

   5. Log out of the VM console.

      [root@vm2 ~]# logout

   Hide Solution