VMmanager cluster node configuration
|Hierarchy:||VMmanager KVM -> VMmanager KVM setup and configuration|
|VMmanager KVM -> Cluster configuration|
|VMmanager Cloud -> VMmanager Cloud setup and configuration|
|VMmanager Cloud -> Cluster configuration|
Supported operating systems:
- CentOS 7 x64 (recommended)
- CentOS 6 x64
We don't recommend that you update operating system of cluster node with major version changing.
We strongly recommend a clean install of VMmanager. You should install a minimal version of the operating system, all the services that VMmanager requires, will be installed automatically during software installation. If your server with VMmanager is supposed to be a cluster node, make sure it meets requirements to cluster nodes.
We don't recommend that you install the software product from a third-party repository.
Be sure to install operating system of the same version on all cluster nodes. The control panel won't allow to add a cluster node if its operating system differs from the one installed on VMmanager server. So, you first need to decide which OS you would like to use for your cluster.
- All cluster nodes must be in the same network
- SSH must listen port 22 on every node
- Multicast between cluster nodes must be allowed (it is not required for KVM version). Multicast between cluster nodes and a storage is not required).Make sure that the "igmp snooping" option is disabled on the switch the servers are connected to. The option activates the protocol which blocks multicast.
- Disable protection from multicast storm, otherwise the cluster nodes diagnostics tool may function incorrectly
- Pay attention to network capacity if you use network storages
Recommended network architecture
All servers should have at least two Ethernet-connections: public IP-address should be configured on the first, and the internal network on the second one. The internal network should be grouped into a single VLAN. When you add new cluster nodes, you need to allocate an IP address from the internal network; public IP address allows to connect clients via VNC
Incoming connections to the following ports must be allowed on cluster nodes:
- 22/tcp - SSH service, from all cluster nodes, and from the public network if needed
- 111/tcp - rpcbind for NFS, from all cluster nodes
- 662/tcp,udp - pftp for NFS, from all cluster nodes
- 892/tcp,udp - NFS, from all cluster nodes
- 1500/tcp - ihttpd, to access to the control panel web-interface from the public network and access the panel services on a cluster node
- 1515/tcp - vmwatch-master monitoring of a VM state, from all cluster nodes on the server with the control panel
- 2049/tcp,udp - NFS, from all cluster nodes
- 32803/tcp - NFS, from all cluster nodes
- 32769/udp - NFS, from all cluster nodes
- 5900-6900/tcp - QEMU VNC. If access to VNC can be performed only via the control panel, the range of ports must be allowed for the network combining cluster nodes
- 15900-16900/tcp - websockify, трансляция QEMU VNC для веб-интерфейса noVNC, access from the public network
- 49152-49261/tcp - сервисы миграции libvirt, from all cluster nodes
If you run VMmanager Cloud, all incoming connections must be allowed from all cluster nodes:
- 5404-5405/udp - corosync multicast, from all cluster nodes. It may vary depending on configuration of cloud functions in the control panel.
- 21064/tcp - dlm, from all cluster nodes
- 41966-41969/tcp - rgmanager, from all cluster nodes
- 50006-50009/tcp - ccsd, from all cluster nodes
- 50007/udp - ccsd, from all cluster nodes
When installing CentOS 7 on cluster nodes we recommend using XFS as the file system.
OS templates that VMmanager uses for guest OS are about 80 gb is size (the largest templates are WIndows - 10-15 GB each template. Every Unix template requires about 100 MB). Templates are located in the /nfsshare/ directory, which is duplicated to each cluster node. Allocate 60-80 Gb of disk space to /nfsshare. If you are planning to install Windows on guest systems or create custom OS templates, you may allocate less space to the partition.
If you are planning to make backup copies, make sure you have in the root section has additional free space: 2,5*<maximum size of vm disk>.
Therefore, we recommend that you allocate 100-150 GB (+ some space for backup copied) for the root partition. The rest of HDD — for /vm, if you are going to use a local file system as a storage, or for the linux-lvm partition if you use a local LVM as a storage.
We can not identify you and respond to your message.