[agentifysh]

proxmox has been great although it comes with a learning curve

back when I used to use cursor I build this mcp but it should work for codex or claude

it lets me easily spin up vms with specs

its tough to create boxes now due to ram prices but got mine at a great time when it was very cheap; i just wish i had bought more then

https://github.com/agentify-sh/cursor-proxmox-mcp

[j45]

Can you share more about the learning curve specifics you're referring to? Thanks.

[INTPenis]

I'm not the person you replied to, but I came from using VMware products for 12 years, to using Proxmox this last 1.5 years.

These are my impressions.

First of all it's a very competent product, mainly thanks to Ceph making it HCI. Without Ceph, I'm not sure what we would do.

It's as effective as you design it, make sure to separate storage and cluster traffic to ensure robustness, and speed. Make sure to use at least 10GbE switch for storage, for fast migrations.

And managing ceph is very important, basically boils down to 1) never let it run out of space, and 2) the more devices you have the easier it is to manage.

Automating against Proxmox definitely is the biggest pain point, and this needs the most work done.

I've spent countless hours, pre-AI, building our automation setup using both Terraform and Ansible. I sort of wish I had tried AI earlier because it does make things easier.

Some things like automating the creation of templates will forever be a complex procedure in Ansible. And I abandoned Terraform completely because the API was too unpredictable for Terraforms strict state, Ansible was a much better fit.

Their AuthZ takes some getting used to, the fact that if you select "Privilege Separation" it countes the user's permissions AND the token permissions, and the token permissions must always be lower than the users.

Templates existing on one node, but taking a unique VM ID across the cluster is also a bit confusing. It means in practice we're always deploying VMs on the same node, before migrating them somewhere else.

[KetoManx64]

When it comes to templates, I shut then down and take a backup, and then just restore that backup to a different node

[INTPenis]

So you deploy a new VM from a template, shut it down, take a backup and then restore that backup to your target node. Is all this done with IaC? Ansible? Even the backup part?

I haven't touched backups with Ansible yet.

[KetoManx64]

Typically I don't touch templates once I do their initial setup, just shut them down and take a backup (can be done using ansible through the PVE CLI)

The backup restore and the VM startup is done through ansible > PVE CLI.

I also have a testing VM that has a "CLEAN" snapshot that I restore to multiple times a day, using ansible > PVE CLI. Once the VM snapshot is restored I turn it back on as well using the PVE CLI

[INTPenis]

Oh I see, your restore of template backup is actually how you deploy a new VM. Interesting!