Proxmox
Proxmox
Proxmox VE Cluster
What is corosync?
◦ It is the communication system for nodes in the cluster
◦ Note : Check the corosync service status
(2) Time Synchronization.
node01 192.168.132.133
node02 192.168.132.134
node03 192.168.132.135
“pvecm” can be used to:
◦ Create a new cluster,
◦ Join nodes to a cluster,
◦ Leave the cluster,
◦ Get status information
◦ Other various cluster related tasks.
No GUI
◦ You cannot create the cluster from GUI
On any node
◦ node01# pvecm create YOUR-CLUSTER-NAME
Network
Node02
The cluster network is the core of a cluster.
All messages sent over it have to be delivered reliable to all
nodes in their respective order.
In Proxmox VE this part is done by corosync, an
implementation of a high performance low overhead high
availability development toolkit.
It serves our decentralized configuration file system (pmxcfs).
This needs a reliable network with latencies under 2
milliseconds (LAN performance) to work properly.
While corosync can also use unicast for communication
between nodes its highly recommended to have a multicast
capable network.
The network should not be used heavily by other members,
ideally corosync runs on its own network.
The /etc/pve/corosync.conf file plays a central role in
Proxmox VE cluster.
It controls the cluster member ship and its network.
For safety: use the pvecm command to configure your cluster
The Proxmox Cluster file system (“pmxcfs”) is a database-
driven file system for storing configuration files.
Files are replicated in real time to all cluster nodes using
corosync.
We use this to store all PVE related configuration files.
The file system is mounted at /etc/pve
Although the file system stores all data inside a persistent
database on disk, a copy of the data resides in RAM.
That imposes restriction on the maximum size, which is
currently 30MB.
This is still enough to store the configuration of several
thousands of virtual machines.
This system provides the following advantages:
◦ seamless replication of all configurations to all nodes in real time
◦ provides strong consistency checks to avoid duplicate VM IDs
◦ read-only when a node loses quorum
◦ automatic updates of the corosync cluster configuration to all
nodes
◦ includes a distributed locking mechanism
Now you must be:
◦ Able to create PVE cluster (add and delete nodes)
◦ Understand Quorum
◦ Understand Proxmox Cluster Filesystem