#PegaProx as a multi-cluster, node & vm manager for #Proxmox based systems is just around the corner!

PegaProx steps in as a real manager with a feature set that you might already know from enterprise solutions which simplifies and standardizes the management of Proxmox based infrastructures.

Each capability focuses on reducing operational complexity while giving operators full control over clusters, nodes, storage, and virtual machines like:

• Unified Multi Cluster Management
• Node and Cluster Monitoring
• User & Group Management
• Semi-automated Node Security Patch Management
• Cross Cluster Migration
• Virtual Machine & Container Management
• CPU Alignment over Nodes for safe VM live-migrations
• Intelligent Load Balancing for VMs
• Intelligent Load Balancing for Storage
• High Availability and Failover
• User-, Group- & Tenancy Management
• And much more...

Instead of just providing and visualizing metrics you can finally completely manage the whole stack: Creating VMs, adding storage, maintenances, PVE node patch management, DRS alike balancing by #ProxLB, CPU compatibility mode for VMs across all nodes (like #ProxCLMC), Tenant support, API and much more!

This will become a game changer for Proxmox users - especially in enterprises which adds all the often requested but missing functions!

You can already find my first insights about it in my blog post: https://gyptazy.com/blog/pegaprox-real-datacenter-manager-proxmox-clusters/

#PVE #enterprise #virtualization #management #python #ProxmoxVE #opensource #ProxLB #ProxCLMC #ProxSnap

@agowa338@chaos.social @txt_file@chaos.social Xen was developed for security, KVM for performance. Nowadays, they don’t differ much in those aspects (even they’re completely different architecturell concepts). One thing was mono-threaded disk devices which came on a par by the count of VM instances but as said, nothing for nowadays anymore.

Today, it’s more about conceptions designs and “orchestrators”. Everyone is talking about Proxmox as a KVM orchestrator/frontend but it also has some major cons. The multi-master architecture with corosync may not fit always (cluster size, latency, distance,..). I crafted a solution for this (#ProxWire https://cdn.gyptazy.com/talks/ProxWire_Connecting_Proxmox_Clusters_Around_the_World_Without_Corosync.pdf) but this also comes with some pitfalls.

With my tools like #ProxLB (bringing in DRS alike resource scheduling which also got invited for a presentation at the Dutch Proxmox Day 2025), #ProxCLMC for something like EVC evaluation, #ProxSnap (snapshot manager), ProxWall (microsegmentation) and #ProxWire, I try to fill the gaps my customers have.

Personally, I like #xcpng really much and it’s closer to the VMware approach while #proxmox might provide a faster quickstart (where often people later run into issues). The best is like always: evaluate your requirements and see which fits best.