Virtual Machine Management

Introduction

The beginning section of this lab will introduce you to the basics of creating and managing VMs in OpenShift Virtualization. Starting with OpenShift 4.19 there is an entirely new UI based on patternfly 6, and a new Virtualization perspective and a tree view for virtual machines that make it easier to visualize and manage your virtualization-based assets. After exploring the UI changes, you will see how the web console guides you through the whole process of creating a virtual machine from a pre-defined template. We will then review the properties of that VM, do some basic management operations, and perform actions like live migration, that are often expected of virtual machine administrators.

Goals

  • Create a new virtual machine

  • Review configurations and options for virtual machines

  • Understand how VM power states are managed using the OpenShift console

  • Live migrate a VM between two hosts

As a reminder, here are your credentials for the OpenShift Console:

Your OpenShift cluster console is available {openshift_console_url}[here^].

Your login is available with:

  • User: {user}

  • Password: {password}

Create a New Project

  1. When you first log in, you will be placed in the Core Platform perspective, with an introductory prompt. Click the Skip tour button to close the window.

    00 Welcome Message

  2. You will be presented with a page that shows all of the projects that your user currently has access to. On this page we will create a new project that will work as our working area for the remainder of this workshop. Click on the Create Project button in the upper right corner.

    01 Create Project

  3. A box will pop up which will give you the opportunity to name this new project, name the project vmexamples-{user} and click the Create button.

    02 Create Project Name
    While the lab guide is designed to be dynamically updated to show your user name correctly, the screenshots are all static images showing user1. Please make sure that you name your project after your assigned user for the workshop that is reflected in your lab guide text.

Switch to the Virtualization Perspective

  1. You will be presented with a view of the OpenShift console inside of your new project. Now it is time to visit the Virtualization view. Click on the Core platform dropdown menu, and select the option for Virtualization once it appears.

    03 Switch Virt View

  2. You will be greeted by an introductory prompt welcoming you to OpenShift Virtualization. Click the check box for Do not show this again and the window will disappear.

    04 Welcome Virt

Exploring OpenShift Virtualization

When you arrive in the Virtualization view you will be on the Overview page which provides a high-level view of all virtualization resources currently in use, lets take a moment to explore.

05 Virt Overview
The Virtualization perspective is available only when Red Hat OpenShift Virtualization is installed and properly configured. In this lab environment the installation and configuration has already been performed for us.

  1. Click on the VirtualMachines item in the left side menu and you will be presented with the virtualization tree view of all VM assets currently in the cluster.

    06 Tree View

  2. Lets explore this page for a few moments: notice that this view is divided into 3 columns, the left-side management menu, the central column for organization of VM-based projects, and then the virtual machine view.

  3. The left menu is the main control for Virtualization integrated functions in OpenShift. We can see virtualization related items like the Catalog, Templates and InstanceTypes to build VMs from, and the menus to configure Storage and Networking options for virtual machines.

    07 Left Menu

  4. The central column as mentioned is a project view. Like other objects in OpenShift, Projects (which are an abstraction for Kubernetes namespaces), are the boundaries for which permissions and other aspects of using and managing the resources are available to a user. By default there is a slider here that only shows projects with existing VMs. Currently the only project that we can see listed is vmimported-{user}, as it is the only project that we have access to with virtual machines in it.

    08 Project Tree

  5. In the virtual machine overview column, it will list place us in the Project mtv-{user} by default, as it’s sorted alphabetically. This project doesn’t currently have any virtual machines in it, nor will it in the future. This view will change when you highlight a specific project or virtual machine in the center column. Lets try that now.

    09 VM List

  6. In the center project view column click on the project vmimported-{user} to see the virtual machines that are currently deployed and available to your specific user account.

    10 VM Imported Project

  7. The vmimported-{user} project will expand listing the three virtual machines that reside there, and the virtual machine overview column will update to show the virtual machines in the vmimported-{user} project. You should see three VMs listed, but they are not currently turned on, these are for a later part of the lab that we can use if necessary.

    11 VMs Stopped

Create a Linux Virtual Machine

  1. To create a virtual machine, we must select the project we would like to create it in.

  2. In the the center project view, click the toggle button to turn off the option for Show only projects with VirtualMachines. This way you can see all of the projects that your user has access to, including the vmexamples-{user} project that we created earlier.

  3. Click on your vmexamples-{user} project and you will see that the virtual machine overview column updates and now has a Create VirtualMachine button.

  4. Click on the Create VirtualMachine button and select From template from the drop-down menu.

    12 Create VM Button
    VMs can also be created from an InstanceType wizard as well as created by entering a custom YAML definition, but for this current lab scenario we are going to stick with creating VMs based on existing templates.

  5. You will be taken to the Catalog screen, where a number of tiles will appear showing the available pre-defined VM templates.

    Reviewing the list of available templates you’ll notice that some have a blue badge which indicates Source available. These are templates which are using automatically downloaded and stored template source disks.

    If you were deploying in your own environment where you can customize the options available, you can choose to modify the availability of these boot sources by default, and/or remove these source disks, in favor of creating custom disks for your organization’s needs.

    13 Create VM Templates

  6. Select the Fedora VM tile, and a dialog opens.

    14 Create VM Quick

  7. Change the name to fedora01 and press Quick create VirtualMachine.

    15 Create VM Quick Name

  8. We will return to our tree view and see information about our new VM in the virtual machine overview column. Notice also that we now see our vmexamples-{user} project listed in the center column as it contains a VM, and that it is highlighted within the project.

    If we watch closely we can see the VM Status switch from Provisioning to Starting and finally Running in the virtual machine overview column when it is ready.

    During this time, the storage provider has cloned the template disk so that it can be used by the newly created virtual machine. The amount of time this takes can vary based on the storage provider being used to create the boot disk, and the current load on the system.

    16 Fedora Running

  9. Once the virtual machine is running we can do some further exploration of the Overview page in the right side column.

    • Details: This tile shows us information about our VM, including it’s name, status, creation time, OS, virtual resources, and the template from which it was created. It also contains a miniature VNC terminal, and the ability to launch a fullscreen web console.

    • General: This tile shows us information specific to OpenShift, including the Namespace (Project), instance name, and Kubernetes pod where the guest is running.

    • Snapshots: This tile gives us information about any existing snapshots, and also has the button to quickly create a snapshot.

    • Network: This tile gives us the IP address of the virtual machine on the software-defined network (SDN) and it’s internal hostname. If no advanced networks are defined, VMs are automatically attached to the pod network. Later in this lab we will explore advanced networking options, and how to customize connectivity for VMs.

    • Utilization: This tile gives us an overview of the resources currently in use by this virtual machine, including CPU, Memory, Storage, and Network throughput.

    • Storage: This tile gives us information about the current storage volumes, for this VM in particular the cloudinit disk that was used to boot the VM from the template, and the virtual hard disk we installed the machine to.

      17 Fedora Details

  10. After you are done looking at the VM details, click the Events tab to see some details of the provisioning process that just took place. If there are any issues with the creation of the VM, they will show up on this tab as well. The following events took place during creation:

    18 Fedora Events

    • A DataVolume was created. DataVolumes are used to manage the creation of a VM disk, abstracting the clone or import process onto OpenShift native storage during the virtual machine’s creation workflow.

    • The new VM instance fedora01 has been started.

Administering Virtual Machines

Administering and using virtual machines is more than simply creating and customizing their configuration. As the platform administrator, we need to be able to control the states of the virtual machine, and perform advanced operations such as live migrations between worker nodes so that we can balance resources, perform maintenance tasks, and reconfigure nodes.

  1. Click the Configuration tab, this is the entry point to obtain more information about, and modify the resources of the virtual machine.

    19 VM Configuration

    It includes seven subtabs:

    20 Configuration Tab

    • Details: This tab presents all of the physical features of the VM in a single panel. From here you can make edits to various descriptors and basic hardware configurations including modifying the cpu or memory, changing the hostname, attaching passthrough devices, and modifying the boot order.

    • Storage: This tab lists the disks attached to the system and allows you to add new disks to the system. If the guest is configured with the agent, it lists the filesystems and the utilization. Here it is possible to attach ConfigMaps, Secrets, and Service Accounts as extra disks. This is useful when passing configuration data to the application(s) running in the virtual machine.

    • Network: This Tab shows the current network interfaces configured for the VM and allows for you to add new ones.

    • Scheduling: This tab includes advanced configuration options indicating where the VM should run and the strategy to follow for eviction. This tab is used to configure (anti)affinity rules, configure node selectors and tolerations, and other behaviors that affect which cluster nodes the VM can be scheduled to.

    • SSH: This tab allows you to configure remote access to the machine by creating an SSH service on a configured load-balancer, or by injecting public SSH keys if the feature is enabled.

    • Initial run: This tab allows us to configure cloud-init for Linux or sys-prep for Microsoft Windows, including setting the commands to be executed on the first boot, such as the injection of SSH keys, installation of applications, network configuration, and more.

    • Metadata: This tab shows current Labels and Annotations applied to the virtual machine. Modifying these values can help us tag our machines for specific purposes, or help us enable automated workflows by uniquely identifying machines.

  2. You can click on each of these to explore at your leisure, but for introductory purposes, lets focus on storage and networking specifically.

  3. List the disks associated with the VM by clicking on the Storage tab:

    21 Storage Tab

    In this environment, the default StorageClass, which defines the source and type of storage used for the disk, is called ocs-external-storagecluster-ceph-rbd. This storage is the default type provided by OpenShift Data Foundation (ODF) for running virtual machines. Each storage provider has different storage classes that define the characteristics of the storage backing the VM disk.

  4. Examine the network interfaces attached to the VM by clicking on the Network subtab:

    22 Network Tab

    When a VM is quick created, an interface on the Pod Networking network of type masquerade is created by default. This connects the VM to the SDN and provides egress from the VM to the world outside the OpenShift cluster. Other VMs, and Pods within the cluster, can access the virtual machine using this interface.

    Furthermore, a VM connected to the SDN can be accessed externally using a Route, or Service with type load balancer, or even have a Network Attachment Definition or User-defined Network (UDN) define a VLAN or external network to directly attach it to. These options will be explored in depth a bit later.

Controlling Virtual Machine State

As a user with granted permissions to manage a Virtualization environment: you can stop, start, restart, pause, and unpause virtual machines from the web console.

  1. Click the Overview tab to return to the summary screen.

  2. In the top right corner you will notice shortcut buttons for running state: stop, restart, pause, and start. As well as a dropdown menu title Actions.

    23 VM State Actions

    • Stop: Starts a graceful shutdown of the Virtual Machine.

    • Restart: This will send a signal to the operating system to reboot the Virtual Machine. Guest integrations are needed for this to work properly.

    • Pause: The process is frozen without further access to CPU resources and I/O, but the memory used by the VM at the hypervisor level will stay allocated.

    • Start: Starts up a stopped virtual machine. It will be greyed out if the machine is running.

  3. While the shortcut buttons are handy, you can also access these options and more by clicking on the Actions menu under the Control menu, and you can also see many other options for interacting with the VM are available in the drop down list.

    24 VM Actions Menu

  4. Press the Stop button and wait until the Virtual Machine is in state Stopped.

    25 VM Stopped

  5. Clicking on Actions and Control, the option Start appears, and the options Restart and Pause are greyed out.

    26 VM Actions List Stopped

  6. Click Start, and wait for the Running status.

  7. Using the Actions menu, or the shortcut button, press the Pause option. The Virtual Machine state will change to Paused.

    27 VM Actions Paused

  8. Have the Virtual Machine resume operations by using the Actions → Control menu and the option Unpause, or by using the shortcut button.

Live Migrate a Virtual Machine

In this section, we will migrate the VM from one OpenShift node to another without shutting down the VM. Live migration requires ReadWriteMany (RWX) storage so that the VM disks can be mounted on both the source and destination nodes at the same time. In most cases OpenShift Virtualization, unlike other virtualization solutions that you may be familiar with, does not use monolithic datastores mounted to each cluster member that hold many VM disks for many different VMs by default. Instead, it makes use of the Kubernetes CSI paradigm where persistent claims are created for each VM disk needed, and each of those disks are stored in its own volume that is only mounted when and where it’s needed.

  1. To see the physical node that the virtual machine is running on, click on the Pod name virt-launcher-fedora01-uuid found under the General tile on the Overview page.

    28 Pod Name

  2. This will bring up the Pod details page. Search for the section header called Node and see the name of the worker that the pod is running on. In this screenshot it is running on worker-cluster-5dktk-1.

    29 Pod Details Node

  3. Click the back button in your browser to return to the Overview page.

  4. Using the Actions menu, select the option for Migration → Compute.

    30 VM Dialog Migrate

  5. You will be presented with a dialog that gives you an option to allow OpenShift to automatically select your destination, or to select a specific node yourself. Leave Automatically selected Node selected, and click the Migrate VirtualMachine button.

    30a Migrate Target Node
    The multiuser nature of this lab environment has RBAC permissions configured in a manner that does not allow for the listing of the nodes in the cluster. In a production use case, you could choose either option.

  6. After a few seconds, the VM will change the status to Migrating, and you can follow it’s progress.

    31 VM Migrating

  7. When the migration is complete the VM will return to the Running status, but it will be running on a new node. Let’s click on our virt-launcher-fedora01-uuid pod name to verify.

    32 Migrated Status

  8. We can now see that the virtual machine is running on a new node, in the image worker-cluster-5dktk-3, and that the pod itself now resides in a new pod with a new unique ID as the live migration process transfers the VM instance to a new pod on a new worker node nondisruptively.

    33 Pod Details Node Migrated

Summary

In this lab, we did an overview of the Virtualization management environment in OpenShift Virtualization, provisioned a virtual machine from template, and performed some basic virtual machine management tasks including: state management and a live migration between physical hosts. Each of these tasks are common and often necessary tasks to be performed as platform administrators and a great way to familiarize yourself with some basic features available when working with VMs in OpenShift Virtualization.