I have installed apticron in order to be notified of available updates. While this works well, I get an e-mail for each node in the cluster. Only one mail would be better.
The next question is: is there a good/recommended way to manage package updates in a cluster?
I think it is quite risky to update many/all nodes at once. First, it creates an unnecessary load spike on the cluster and second, if the updates somehow leaves the system in a faulty state, it would affect multiple nodes at once. Therefore I strive to to updates one after another. For such a daisy chained update automation would be really nice.
Obviously, one could use to GUI to update each node. But the larger the cluster gets, the more clicking is involved.
Using a multi ssh approach like Parallel SSH, Ansible, etc. has the drawback of doing updates in parallel, which might be a bad idea as stated above.
Is there a better solution?
Does Proxmox plan to implement some kind of centralized (or corosync-based) update-notification and update-installtion mechanism?
The next question is: is there a good/recommended way to manage package updates in a cluster?
I think it is quite risky to update many/all nodes at once. First, it creates an unnecessary load spike on the cluster and second, if the updates somehow leaves the system in a faulty state, it would affect multiple nodes at once. Therefore I strive to to updates one after another. For such a daisy chained update automation would be really nice.
Obviously, one could use to GUI to update each node. But the larger the cluster gets, the more clicking is involved.
Using a multi ssh approach like Parallel SSH, Ansible, etc. has the drawback of doing updates in parallel, which might be a bad idea as stated above.
Is there a better solution?
Does Proxmox plan to implement some kind of centralized (or corosync-based) update-notification and update-installtion mechanism?
