Managing Virtual Machines with Red Hat OpenShift Virtualization

Open a web browser on the workstation machine and navigate to the OpenShift web console at https://console-openshift-console.apps.ocp4.example.com. Log in to your OpenShift cluster as the admin user with redhatocp as the password.

1. Open a web browser and navigate to https://console-openshift-console.apps.ocp4.example.com. Select htpasswd_provider and log in as the admin user with redhatocp as the password.

Clone the golden-web VM to a new VM named web1.

1. The cloning process requires that you stop the source machine. Navigate to Virtualization → VirtualMachines, select the golden-web VM, and then click Actions → Stop to stop the VM. Wait for the machine to stop.

2. Click Actions → Clone. Set the VM name to web1, select Start VirtualMachine on clone, and then click Clone.

3. Navigate to Virtualization → VirtualMachines and confirm that the new web1 VM is running.

4. Repeat this step to create a clone named web2.

Take a snapshot of the web1 VM. The name of the snapshot must be web1-snap1.

1. Select the web1 VM, navigate to the Snapshots tab, and then click Take Snapshot.

2. Enter web1-snap1 in the Name field and then click Save.

3. Wait for the snapshot to report the Succeeded status.

The web servers that are running inside the web1 and web2 VMs expose the /cgi-bin/health endpoint that you can use to monitor the application status. Add a readiness probe to the web1 and web2 VMs that uses HTTP GET requests to test the /cgi-bin/health endpoint.

1. Navigate to Virtualization → VirtualMachines, select the web1 VM, and then navigate to the YAML tab. Use the YAML editor to declare the probe and then click Save.

   You can copy and paste the readinessProbe section from the /home/student/DO316/labs/review-cr3/readiness.yaml file that the lab command prepares.

   apiVersion: kubevirt.io/v1
   kind: VirtualMachine
   metadata:
   ...output omitted...
   spec:
     ...output omitted...
     template:
       metadata:
       ...output omitted...
       spec:
         domain:
           ...output omitted...
         readinessProbe:
           httpGet:
             path: /cgi-bin/health
             port: 80
           initialDelaySeconds: 60
           periodSeconds: 5
           timeoutSeconds: 2
           failureThreshold: 2
           successThreshold: 1
         evictionStrategy: LiveMigrate
         hostname: web1
   ...output omitted...

2. Restart the web1 VM to apply the changes. Click Actions → Restart and wait for the VM to reach the Running status before proceeding.

3. Repeat this step to add the readiness probe to the web2 VM.

Attach the web1-documentroot PVC as a disk to the web1 VM by using the virtio interface. Repeat this step to attach the web2-documentroot PVC as a disk to the web2 VM.

1. Use the OpenShift web console to stop the web1 VM. Navigate to Virtualization → VirtualMachines, select the web1 VM, and then click Actions → Stop. Wait for the machine to stop.

2. Navigate to the Configuration tab and select Disks. Click Add Disk. Complete the form by using the following information:

   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
   Source	Use an existing PVC
   PersistentVolumeClaim	web1-documentroot
   Type	Disk
   Interface	virtio

   Click Add to attach the disk to the VM.

3. Click Actions → Start to start the VM.

4. Repeat this step to attach the web2-documentroot PVC to the web2 VM.

Log in to the web1 VM console as the root user with redhatocp as the password. Then, run the /root/mount.sh script. Repeat this step for the web2 VM.

1. Navigate to Virtualization → VirtualMachines, select the web1 VM, and then navigate to the Console tab.

2. Log in to the VM console as the root user with redhat as the password.

3. Run the /root/mount.sh command.

   [root@golden-web ~]# /root/mount.sh
   ...output omitted...
   Mount successful

4. Log out of the VM console.

   [root@golden-web ~]# logout

5. Repeat this step to mount the disk on the web2 VM.

Add the tier: front label to the virt-launcher pods for the web1 amd web2 VMs.

1. Navigate to Virtualization → VirtualMachines, select the web1 VM, and then navigate to the YAML tab.

2. In the YAML editor, add the tier: front label in the .spec.template.metadata.labels path.

   ...output omitted...
   spec:
     dataVolumeTemplates:
     ...output omitted...
     template:
       metadata:
         creationTimestamp: null
         labels:
           tier: front
           flavor.template.kubevirt.io/small: "true"
           kubevirt.io/domain: golden-web
           kubevirt.io/size: small
           ...output omitted...

3. Restart the web1 VM to apply the changes. Click Actions → Restart and wait for the VM to reach the Running status before proceeding.

4. Repeat this step to add the same label to the web2 VM.

Create a service named front with the ClusterIP type. Use the tier: front label for the selector. The service must listen on TCP port 80 and forward the traffic to the VM on port 80.

1. From the OpenShift web console, navigate to Networking → Services.

2. Click Create Service and then use the YAML editor to create the front service with the following content:

   apiVersion: v1
   kind: Service
   metadata:
     name: front
     namespace: review-cr3
   spec:
     type: ClusterIP
     selector:
       tier: front
     ports:
       - protocol: TCP
         port: 80
         targetPort: 80

   The lab command prepares the /home/student/DO316/labs/review-cr3/service.yaml file as an example.

3. Click Create to create the service. The Details tab for the front service is displayed.

4. Confirm that the front service has two active endpoints. Click the Pods tab and confirm that list includes the virt-launcher pods for the web1 and web2 VMs.

Create a route to access the web application that is running inside the VMs by using the http://front-review-cr3.apps.ocp4.example.com URL.

1. From the web console, navigate to Networking → Routes. Click Create Route and complete the form by using the following information:

   Field	Value
   Name	front
   Service	front
   Target port	80→ 80 (TCP)

   Click Create.

2. From a command-line window on the workstation machine, use the curl command to confirm that you can access the web application from outside the cluster.

   [student@workstation ~]$ curl http://front-review-cr3.apps.ocp4.example.com
   <!doctype html>
   <html lang="en">
   <head>
     <title>Test page web2</title>
   </head>
   
   <body>
     <h1>Test Page web2</h1>
      Welcome to web2.
   </body>
   </html>

3. Rerun the curl command several times to confirm that the service dispatches the requests between the two VMs.

   [student@workstation ~]$ curl http://front-review-cr3.apps.ocp4.example.com/?[1-3]
   --curl--front-review-cr3.apps.ocp4.example.com/?1
   <!doctype html>
   <html lang="en">
   <head>
     <title>Test page web2</title>
   </head>
   
   <body>
     <h1>Test Page web2</h1>
      Welcome to web2.
   </body>
   </html>
   
   [2/3]: front-review-cr3.apps.ocp4.example.com/?2 --> <stdout>
   --curl--front-review-cr3.apps.ocp4.example.com/?2
   <!doctype html>
   <html lang="en">
   <head>
     <title>Test page web1</title>
   </head>
   
   <body>
     <h1>Test Page web1</h1>
      Welcome to web1.
   </body>
   </html>
   
   [3/3]: front-review-cr3.apps.ocp4.example.com/?3 --> <stdout>
   --curl--front-review-cr3.apps.ocp4.example.com/?3
   <!doctype html>
   <html lang="en">
   <head>
     <title>Test page web2</title>
   </head>
   
   <body>
     <h1>Test Page web2</h1>
      Welcome to web2.
   </body>
   </html>