You can explore the features and functionalities of OKD Virtualization by installing and configuring a basic environment.
Cluster configuration procedures require |
You can start exploring OKD Virtualization by taking tours in the OKD web console.
This short guided tour introduces several key aspects of using OKD Virtualization. There are two ways to start the tour:
On the Welcome to OKD Virtualization dialog, click Start Tour.
Go to Virtualization → Overview → Settings → User → Getting started resources and click Guided tour.
Quick start tours are available for several OKD Virtualization features. To access quick starts, complete the following steps:
Click the Help icon ? in the menu bar on the header of the OKD web console.
Select Quick Starts.
You can filter the available tours by entering the keyword virtualization
in the Filter field.
Plan and install OKD Virtualization on an OKD cluster:
Create a virtual machine (VM):
Create a VM from a Red Hat image.
You can create a VM by using a Red Hat template or an instance type.
You can create a VM by importing a custom image from a container registry or a web page, by uploading an image from your local machine, or by cloning a persistent volume claim (PVC).
Connect a VM to a secondary network:
Single Root I/O Virtualization (SR-IOV) network.
VMs are connected to the pod network by default. |
Connect to a VM:
Connect to the serial console or VNC console of a VM.
Manage a VM:
To migrate virtual machines from an external provider such as VMware vSphere, OpenStack, Red Hat Virtualization, or another OKD cluster, use the Migration Toolkit for Virtualization (MTV). You can also migrate Open Virtual Appliance (OVA) files created by VMware vSphere.
Migration Toolkit for Virtualization is not part of OKD Virtualization and requires separate installation. For this reason, all links in this procedure lead outside of OKD Virtualization documentation. |
The Migration Toolkit for Virtualization Operator is installed.
Configure the source provider.
Select the source provider and enter any required information, such as the URL of the API endpoint or credentials needed to access the virtual machines.
Select from the list of available virtual machines, configure the target provider, and define storage and network mappings.
Watch the progress, view migration logs, or cancel the migration.
Optional: Archive the migration plan.
After confirming that the migration has completed successfully, you can archive the migration plan to delete the logs and clean up all temporary resources created during migration. You can permanently delete an archived migration plan.