Hello, and welcome to this presentation on upgrading a KVM host in Oracle Linux Virtualization
Manager.
In this video you will learn to identify important items to consider when upgrading a KVM host.
Enable required Oracle Linux Yum repositories and install the repository configuration file
on the KVM host.
Demonstrate upgrading a KVM host in the Oracle Linux Virtualization Manager Administration
Portal.
Disable the repositories after upgrading.
And demonstrate changing the cluster and data center compatibility versions.
Before upgrading, there are some items which must be given consideration.
With migration enabled at the cluster level, the virtual machines automatically migrate
to another host in the cluster.
A cluster must contain more than one host before performing an upgrade.
So, consider upgrading hosts one at a time because one host must remain available to
perform Storage Pool Manager, or SPM, tasks.
When you upgrade a host, virtual machines are migrated to other hosts in the cluster.
Therefore, clusters need sufficient memory reserve, otherwise a virtual machine migration
can fail.
Shutting down virtual machines before updating the host can reduce the memory usage impact
of virtual machine migration.
You cannot migrate a virtual machine using a virtual Graphics Processing Unit, or vGPU,
to a different host.
Virtual machines with vGPUs installed must be shut down before updating the host.
The first thing we need to do is install the oracle-ovirt-release-el7 package on the host.
If needed, enable the repository called ol7_latest for the latest Oracle Linux packages, and
then install the package.
Here the command yum repolist enabled ol7_latest is used to check if the repository is already
enabled.
Next, the command yum install oracle-ovirt-release-el7 installs the required package.
During the installation, the repository file is copied into the /etc/yum.repos.d directory,
and the required ol7_x86_64_ovirt43 and ol7_x86_64_ovirt43_extras repositories are enabled.
These two repositories provide access to the latest release of the software used to upgrade
the KVM host.
Now, we can look at upgrading a KVM host from Release version 4.2 to 4.3.
After a successful upgrade, we disable the ovirt-4.2 and the ovirt-4.2-extra repositories.
Disabling the repositories ensures that any future or intermediate upgrades of KVM hosts
use the current release.
The screen capture on the slide shows a sequence of commands to illustrate disabling the oVirt
4.2 repositories.
The command yum repolist enabled *ovirt* lists all oVirt enabled repositories.
The output shows both the oVirt 4.2 and oVirt 4.3 repositories are enabled.
To disable the oVirt 4.2 repositories, I use the command yum-config-manager --disable ovirt-4.2.
In this video, we will upgrade the KVM host ovs025.
If this were a production environment, we would perform these steps on each host.
We are viewing the Hosts pane in the Administration portal.
We select the ovs025 host from the list in the table.
Then we click the Installation button and select Check for Upgrade from the drop-down
menu.
This opens an Upgrade Host confirmation dialog window.
We click OK to initiate the check process, with the Manager host checking the KVM host
to see if it requires an upgrade.
To monitor the checking process, click the Events button, the bell icon in title bar
of the Administration Portal window.
In the Events list dialog we can monitor the progress.
The first event shows that the check has begun.
Soon after, the check for updates process finishes indicating successful completion,
and indicates a list of packages to update.
And the host is reactivated.
We click the Events button again to close the list.
To proceed with the upgrade, we click the Installation drop down button and select Upgrade.
From the Upgrade Host window, we will keep the Reboot host after upgrade selected.
The dialog states there are VMs running which will be automatically migrated.
We click OK to begin the upgrade process.
Returning to the Events view, we can monitor the upgrade process.
The host is first is switched to Maintenance Mode, followed by the migration of any VMs
running on the host.
We also get notifications on the migration status.
The next events we see are notifications that the restarting of host has begun.
The host reboots and after some time the triangle icon next to the host turns red.
With a final notification that host is active and running, and the triangle is now green.
After closing the Events messages the icon indicating an upgrade for our host is cleared.
We can see the other host ovs018 has the upgrade icon showing, so if we wanted to upgrade this
host also, we would follow the same steps.
Our next demonstration will cover the post-upgrade task of switching the compatibility versions
of the Cluster and Data Center.
Cluster compatibility version indicates the features of Oracle Linux Virtualization Manager
supported by all of the hosts in the cluster.
For more information on compatibility versions, refer to the Post-Upgrade Data Center and
Cluster Compatibility Versions section of the Oracle Linux Virtualization Manager Getting
Started Guide.
All of our hosts will run release version 4.3, so we will change the Cluster compatibility
to 4.3 to support the 4.3 features and to ensure we do not have issues.
In the Administration Portal, go to Compute and click Clusters.
Select the cluster to change and click Edit.
We only have one cluster, the Default cluster, so this is the one we will use.
From the Edit Cluster dialog box, select the General tab.
From the Compatibility Version drop down, we select 4.3 and click OK.
We select 4.3 to match the release version we upgraded the host to.
On the Change Cluster Compatibility Version confirmation window, click OK.
Now we need to change the compatibility version of the Data Center.
To do this, we navigate to Compute and then Data Centers.
Click on the data center row in the table to be changed and click Edit.
From the Edit Data Center dialog box, change the Compatibility Version drop down to the
desired value, 4.3 in our case, and click OK.
On the Change Data Center Compatibility Version confirmation window, it warns us that making
this change may affect any Storage Domains associated with the Data Center.
These need to be upgraded to the same version also.
We click OK.
A pop up message tells us the editing is complete.
We have now updated the compatibility version of the data center.
In this video you learned to identify important items to consider when upgrading a KVM host.
Enable required Oracle Linux Yum repositories and install the repository configuration file
on the KVM host.
Demonstrate upgrading a KVM host in the Oracle Linux Virtualization Manager Administration
Portal.
Disable the repositories after upgrading.
And demonstrate changing the cluster and data center compatibility versions.
Look to the links provided here to access a vast number of resources that you can use
to discover more about this subject and others in the Oracle Learning Library.
Thats the end of the video, thanks for watching.