VMmanager principles

From ISPWiki
Jump to: navigation, search
Hierarchy: VMmanager KVM -> Introduction to VMmanager KVM

Control panel

VMmanager KVM uses the KVM hardware virtualization. It utilizes libvirt to manage virtualization. VMmanager KVM supports multiple threading, i.e. it can process a few requests simultaneously. One VMmanager KVM is able to manage a number of physical servers (cluster nodes). You can install the control panel either on a dedicated server or on a virtual machine. We recommend installing it on a dedicated server, as in this case the server with VMmanager KVM installed can be used as one of the cluster nodes.

Cluster nodes

A cluster is a group of servers with virtual machines running on them. Cluster nodes are physical servers. VMmanager is homogenous: all cluster nodes are to have the same operating system, while all storages and networks are connected to all cluster nodes automatically. This allows for live migration of virtual machines between the nodes. Read more about clusters: Cluster node configuration, Adding cluster nodes.


Every virtual machine requires a virtual disk: a disk image connected to the virtual machine. Virtual disks are stored in a local (LVM, file system) or a network (network LVM, iSCSI, RBD, GlusterFS, NFS) storage. Read more about storage: How to connect storages.


You can create new virtual machines faster with templates of virtual machines (VM template). A template is a group of settings used to create new virtual machines. It can be RAM, number of CPUs, processor priority, disk space, etc. In a similar fashion, there are templates of operating systems (OS template) used to facilitate operating system installation. These are sets of disk images and installation scripts, consisting of distributives and other data needed for operating system installation. More about VM templates: VM templates. More about OS templates: Category:Operating system templates.


Recipes are used to accelerate preparation of a virtual machine. They allow installing any software for specific tasks after OS had been installed on a virtual machine. More about recipes: Recipes.


VMmanager creates a virtual network bridge which unites the network interface of a cluster node and network interfaces of virtual machines. This way it establishes static routing for virtual machines: it adds a static public IP address to the network interface of a virtual machine and specifies network mask and gateway. Furthermore, the control panel can create virtual machines with private IP addresses; in this case, NAT is used to establish access to the web. More about networks: Category:Networks.

Backup system

VMmanager KVM has the built-in backup system for virtual machines, as well as for VMmanager itself. This system is quite flexible and is able to create backup copies of specific virtual machines and/or the control panel. Backup can be scheduled for specific time and periodicity, on a local disk or remote FTP storage. Only VMmanager administrator can create and restore backup copies. More about backup system: VMmanager: Backup configuration.