7. Keeping Your System Up To Date¶
This chapter explains how to keep the software on Virtuozzo Hybrid Server nodes up to date.
Important
It is strongly recommended to have all nodes run the same version of Virtuozzo Hybrid Server. At the very least make sure that product versions are only one major update apart. For example, before you update a node to Virtuozzo Hybrid Server 7.0 Update 7, make sure that all other machines in the cluster already run Update 6. The reason is that VMs created on newer nodes may fail to start on older nodes, thus causing issues with migration, restore from backup, high availability, and such.
The components that may need updating are:
Virtuozzo Hybrid Server software:
Tools and libraries
ReadyKernel patch
Kernel (typically included in major updates)
Virtual machines and containers hosted on the node:
Container EZ templates
KVM/QEMU hypervisor and guest tools in virtual machines
You can update Virtuozzo Hybrid Server nodes in several ways:
Automatically (default)
Automatically using smart updates
Manually using
yum, the standard tool for RPM-based Linux operating systems
All of these methods as well as ways to update the kernel, virtual machines, and containers are described further in this chapter.
In this chapter:
- 7.1. Updating Overview
- 7.2. Using A Proxy Server to Install Updates
- 7.3. Updating Automatically
- 7.4. Updating Automatically with Smart Updates
- 7.4.1. Enabling Smart Updates
- 7.4.2. Checking Node Status
- 7.4.3. Setting the Maintenance Window and Schedule
- 7.4.4. Setting the Repositories
- 7.4.5. Excluding RPM Packages and ReadyKernel Patches from Updates
- 7.4.6. Changing Node Update Policies
- 7.4.7. Suspending Updates for All or Specific Nodes
- 7.4.8. Disabling Smart Updates
- 7.5. Updating Manually
- 7.6. Updating Nodes in Virtuozzo Storage Clusters
- 7.7. Updating the Kernel
- 7.8. Updating the Kernel with ReadyKernel
- 7.9. Updating Software in Virtual Machines
- 7.10. Updating Containers
- 7.11. Downgrading to Older Versions