Proxmox — upcoming versions & roadmap
What is under development for an upcoming CMP version versus what remains on the longer roadmap.
Supported features today: Proxmox VE Capabilities & Explorer.
Under development — available in upcoming version
These items are under development and are expected in an upcoming version. They are not general roadmap placeholders.
Networking — Proxmox SDN
| Status | Under development — available in an upcoming version |
|---|
Native CMP support for Proxmox SDN (zones, vnets, and related SDN objects).
Today: Import and IPAM use conventional Proxmox networks (for example Linux bridges such as vmbr0). See Networks and Networks and IPAM.
Upcoming: Deeper integration with Proxmox SDN so CMP can manage or consume SDN zones and virtual networks.
Until SDN ships, create Linux bridges on Proxmox and sync / import them into CMP. CMP does not provision networks on Proxmox today.
Backups — destination improvements
| Status | Supported & Available (Local Datastores + PBS) |
|---|
CMP now supports dedicated backup storages and automated destination selection for Proxmox VE.
- Local Proxmox Storage:
vzdumparchives to designated local backup pools. - Proxmox Backup Server (PBS): Enterprise chunk-based, deduplicated, and encrypted backup destination.
- Storage Selection Algorithm: When multiple backup storages are configured in CMP, the platform automatically selects the optimal destination based on capacity and load.
For configuration requirements and API permissions, see Backup & Recovery.
Roadmap
Only the item below is on the roadmap (not scheduled as an upcoming-version deliverable in the same way as SDN and backup destinations).
Associated IP / NAT mapping (automation)
| Status | Roadmap (manual today) |
|---|---|
| Today | Admins set Associated IP Address on private IPAM rows for display only — see Associated IP Address (NAT representation) and IPAM |
| Gap | CMP does not create or discover NAT; private ↔ public mapping is manual |
Suggested automation (open to implement)
Practical options, from lighter to stronger:
| Approach | What CMP could do | Notes |
|---|---|---|
| 1. Bulk CSV / import mapping | Admin uploads private_ip,public_ip pairs for a network | Fast win; still admin-owned NAT on the edge |
| 2. 1:1 pool pairing | Define a public pool next to a private pool and auto-assign associated public IPs in order when private IPs are generated | Good when NAT is static 1:1 and ranges align |
| 3. Edge / firewall API sync | Read DNAT / SNAT rules from a supported firewall or Proxmox helper API and fill Associated IP Address | Needs a reliable source of truth; hardest but least drift |
| 4. Customer-visible only after verify | Optional health check (ICMP / TCP probe of public IP) before showing the association in the portal | Improves trust; does not configure NAT |
Recommended first step: implement (1) bulk import and (2) 1:1 pool pairing in CMP. Keep NAT configuration on Proxmox / the edge; use CMP only to keep the representation accurate for customers until a sync source (3) is available.
Related
- Proxmox VE Capabilities & Explorer
- Backup — available today; docs in progress
- Networks
- IPAM
- Connecting CMP to Proxmox
- Networks and IPAM
- Proxmox VE Setup