Repository navigation
v0.15.0: Proxmox clusters
dash now reads your whole Proxmox VE cluster through its one Proxmox connection (#46): every node, the cluster's quorum, totals, and every guest and storage on its own node. A minor release: some payloads change shape; the settings do not.
New
- Clusters through one connection. dash asks whichever node
plugins.proxmox.urlreaches for the whole cluster. A standalone server is a cluster of one. - VMs page:
- a cluster summary: name, quorum, nodes online, and the CPU, memory and storage totals of the online nodes;
- a card per node: its state, CPU, memory, uptime, Proxmox VE version, CPU model and guests;
- each VM and template shows its node, and the activity table has a Node column.
- Per-VM calls go to the right node. A VM's detail and console use its own node, follow a guest that just migrated, and answer at once for a guest of an offline node.
- Storage: every node's storages, a shared one (NFS, Ceph) listed and counted once, with totals.
- Overview: the topology draws one host per node, each VM under its node.
- Attention: an offline node and a cluster that lost quorum are critical items.
- Hardware page: the Proxmox facts of the host's own node.
Upgrade notes
- Settings: nothing to change.
plugins.proxmox.nodeno longer chooses what dash reads; it names the node the Hardware page's host is. A cluster of several nodes no longer needs it for the plugin to run, but its Hardware page does (orplugins.hardware.hosts[0].nodename). - Token: the cluster's name and quorum need
Sys.Auditon/(PVEAuditoron/has it). Without it everything else works and the quorum reads as unknown. - API and clients:
proxmox.nodeis replaced byproxmox.cluster;- VMs and tasks carry
node; - storage refs carry the node (
proxmox:Storage/<node>/<name>; a shared one isproxmox:Storage/<name>); core.overview's topology hashosts(one per node) instead ofhost.
- Rolling back to v0.14.11: no settings change, but a cluster of several nodes then needs
plugins.proxmox.nodeagain.
See docs/upgrading.md.