Hoping to get a little input here from anybody using apcupsd (or NUT) to shutdown a Proxmox cluster.
I've been working on a suite of applications that containerize apcupsd, apcupsd-cgi, a TIG stack (Telegraf, InfluxDB2, Grafana for dashboard-style monitoring), and a Wake-on-LAN container for bringing systems back online after power is restored. It's all working well for traditional Linux (with Docker) and Windows environments. Next I'd like to get this suite of applications rocking-and-rolling with Proxmox.
Additional info on this project if you're interested:
https://www.reddit.com/r/homelab/comments/1359851/managing_multiple_apc_ups_units_including/
https://technologydragonslayer.com/...onitoring-with-apcupsd-admin-plus-and-docker/
I've been busy virtualizing "everything" on my network, and have seen first-hand the challenges with shutting Proxmox clusters without running into issues with quorum. My first thought in terms of an orderly shutdown (in the event of a power failure), is to install apcupsd (as a slave) in each container and virtual machine running in the Proxmox cluster. Based on the Googling I've done, this appears to be an important first step in shutting down a cluster. This should work, though obviously not everybody installs Docker in every CT or VM. apcupsd can, of course, be installed without being containerized -- which works well, but can get to be a bit of a juggling act when running on dozens of "slaves'.
I've been experimenting with the Proxmox API for shutdowns, and that works quite well for a single instance of Proxmox. What I'm wondering, particularly from those of you who've been in the trenches with this issue -- is there a way to scale an API shutdown to a cluster? For example, does the API support first shutting down all CTs/VMs and then shutting down the cluster? And if so, what's the syntax for that API call using curl?
I've been working on a suite of applications that containerize apcupsd, apcupsd-cgi, a TIG stack (Telegraf, InfluxDB2, Grafana for dashboard-style monitoring), and a Wake-on-LAN container for bringing systems back online after power is restored. It's all working well for traditional Linux (with Docker) and Windows environments. Next I'd like to get this suite of applications rocking-and-rolling with Proxmox.
Additional info on this project if you're interested:
https://www.reddit.com/r/homelab/comments/1359851/managing_multiple_apc_ups_units_including/
https://technologydragonslayer.com/...onitoring-with-apcupsd-admin-plus-and-docker/
I've been busy virtualizing "everything" on my network, and have seen first-hand the challenges with shutting Proxmox clusters without running into issues with quorum. My first thought in terms of an orderly shutdown (in the event of a power failure), is to install apcupsd (as a slave) in each container and virtual machine running in the Proxmox cluster. Based on the Googling I've done, this appears to be an important first step in shutting down a cluster. This should work, though obviously not everybody installs Docker in every CT or VM. apcupsd can, of course, be installed without being containerized -- which works well, but can get to be a bit of a juggling act when running on dozens of "slaves'.
I've been experimenting with the Proxmox API for shutdowns, and that works quite well for a single instance of Proxmox. What I'm wondering, particularly from those of you who've been in the trenches with this issue -- is there a way to scale an API shutdown to a cluster? For example, does the API support first shutting down all CTs/VMs and then shutting down the cluster? And if so, what's the syntax for that API call using curl?
