So I'm still very much in the lab stage and pre-production here, and I'm still growing storage and have a maintenance window every month where I have to shut down everything except the two VMs that provide the storage (The SAN and NAS nodes). Obviously, when the SAN goes down for updates, Proxmox can't access the iscsi shares and so everything on it needs to get shut down. This is fine, but...
So I go through all the VMs one at a time and shut them down. All except the NAS and SAN VMs. Then I do my maintenance, then I start up all the VMs one at a time. This is very tedious.
What I would like to do is press a button in the UI, though I'd settle for a command on the command line, and have proxmox just automatically start all the VMs that were stopped according to their onboot start order, honouring delays and orderings, et al. It would also be nice if I could automate "Put this storage in maintenance mode, which means shut down every VM that depends on it, honouring the reverse start order, including the VMs that depend on those VMs", but that would require modelling dependencies in Proxmox, and I'm pretty sure we aren't there yet.
So I go through all the VMs one at a time and shut them down. All except the NAS and SAN VMs. Then I do my maintenance, then I start up all the VMs one at a time. This is very tedious.
What I would like to do is press a button in the UI, though I'd settle for a command on the command line, and have proxmox just automatically start all the VMs that were stopped according to their onboot start order, honouring delays and orderings, et al. It would also be nice if I could automate "Put this storage in maintenance mode, which means shut down every VM that depends on it, honouring the reverse start order, including the VMs that depend on those VMs", but that would require modelling dependencies in Proxmox, and I'm pretty sure we aren't there yet.
