gyptazy.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Site description
Only tech related content - nothing else!
Admin email
contact@gyptazy.com

Search results for tag #qualvosec

7 ★ 6 ↺

[?]o gyptazy »

Hey community! I would like to hear your thoughts on how you usually update your Proxmox nodes and clusters. How do you handle minor Proxmox and package upgrades with ?

What would you think about a new API endpoint that lets you run unattended upgrades with a simple call like:

/nodes/{node_name}/apt/upgrade
At the moment you need to use the node’s HTML5 console to perform upgrades. Other methods exist such as running unattended Debian upgrade scripts, using patch management tools like or , or automating the process with over SSH. My idea is to have an API based solution that relies on Proxmox authentication and authorization. This would also allow third party tools such as to provide automated patch management and even handle guest rebalancing in a way that is similar to DRS without requiring direct SSH access.
I have already been running this approach on several internal clusters since the release of PVE 8 without issues. Now I am interested to hear if you would use unattended upgrades in general or if you are already running them today.


A Proxmox Node running apt-get -y dist-upgrade command via API in a non interactive and unattended way by a patched and extended API from gyptazy

Alt...A Proxmox Node running apt-get -y dist-upgrade command via API in a non interactive and unattended way by a patched and extended API from gyptazy