Managing Virtual Machines with Red Hat OpenShift Virtualization

Instructions

1. Use the OpenShift web console to confirm that the two VMs are running.

   1. 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.

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

   2. Navigate to Virtualization → VirtualMachines and select the storage-intro project. Confirm that the vm1 and vm2 VMs are running.

2. Prepare a 5 GiB blank disk for the vm1 database server. Attach the disk to the VM by using a virtio interface. Use the ocs-external-storagecluster-ceph-rbd-​virtualization storage class, which provides fast block storage.

   1. Stop the vm1 VM so that you can use the virtio interface to attach the new disk. Remember that the only available interface is scsi when the VM is running.

      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 and then click Add disk. Complete the form by using the following information and click Save to create and attach the disk to the VM.

      Field	Value
      Use this disk as a boot source	Unset
      Name	dbdata
      Source	Blank (creates PVC)
      Size	5 GiB
      Type	Disk
      Interface	VirtIO
      StorageClass	ocs-external-storagecluster-ceph-rbd-​virtualization
      Apply optimized StorageProfile settings	Checked
      Acces mode	Shared access (RWX)
      Volume mode	Block
      Enable preallocation	Unset

      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 stopped.

   3. Click Actions → Start to start the vm1 VM.

      Note

      If a yellow admonition appears, then wait a few moments and try again to start the VM.

   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@vm1 ~]# 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     1M    0   disk
      vdc      252:32     0     5G    0   disk	

      The vdc block device corresponds to the new disk that you added in a previous step.

   5. Log out of the VM console.

      [root@vm1 ~]# logout

3. Prepare a 10 GiB blank disk for the vm2 web server. Attach the disk to the VM by using a virtio interface. Use the nfs-storage storage class.

   1. Navigate to Virtualization → VirtualMachines and then select the vm2 VM.

   2. Stop the vm2 VM so that you can use the virtio interface to attach the new disk. Click Actions → Stop to stop the vm2 VM. Click Stop to confirm the operation, if needed. Wait for the machine to stop.

   3. Navigate to the Configuration → Disks tab and then click Add disk. Complete the form by using the following information. At the bottom of the form, notice that the volume mode is set to Filesystem by default. Do not change that parameter. Click Save to create and attach the disk to the VM.

      Field	Value
      Use this disk as a boot source	Unset
      Name	staticdata
      Source	Blank (creates PVC)
      Size	10 GiB
      Type	Disk
      Interface	VirtIO
      StorageClass	nfs-storage
      Apply optimized StorageProfile settings	Checked
      Access mode	Shared access (RWX)
      Volume mode	Filesystem
      Enable preallocation	Unset

   4. Click Actions → Start to start the vm2 VM.

   5. Log in to the VM console and confirm that a new 10 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 10 GiB vdc block device.

      Note

      Even though you create the volume in Filesystem mode, OpenShift Virtualization exposes the volume as a block device to the operating system inside the VM. As a consequence, the lsblk command that you run inside the VM reports the volume as a new 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     1M    0   disk
      vdc      252:32     0    10G    0   disk	

      The vdc block device corresponds to the new disk that you added in a previous step.

   6. Log out of the VM console.

      [root@vm2 ~]# logout

4. Detach the additional disk from the vm2 VM.

   1. Click Actions → Stop to stop the vm2 VM.

   2. Navigate to the Configuration → Disks. At the end of the row of the staticdata disk, click the vertical ellipsis icon ⋮ and then click Detach. Click Detach in the confirmation window.

   3. Click Actions → Start to start the vm2 VM.

   4. Log in to the VM console and confirm that the device no longer exists. 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 that the command no longer reports the vdc 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     1M    0   disk

   5. Log out of the VM console.

      [root@vm2 ~]# logout