20 docs tagged with "proxmox"

StackConsole CMP provides integrated virtual machine backup and recovery for Proxmox VE, supporting both local Proxmox datastores and enterprise Proxmox Backup Server (PBS) integration.

IP Address packages define how IPs are priced on the rate card for a Proxmox setup and zone. CMP allocates addresses from the pools you manage in Networks and IPAM; this package is the billing side of those IPs.

Connect CMP to Proxmox VE so CMP can authenticate to the Proxmox API and provision VMs, storage categories, networks, and related services.

CMP bills network IPs from a single IP Address package per Cloud Provider Setup + Zone. Configuring prices is the same whether the IP is acquired at VM create or on a network with IP billing enabled.

IPAM (IP Address Management) for Proxmox in CMP is a CMP-level capability. Proxmox does not provide the IP pool, allocation tracking, or billing subscription lifecycle that CMP uses for customer VMs — CMP owns that layer.

How networking works for Proxmox VE in CMP after the provider is connected.

After Connecting CMP to Proxmox, configure network categories, import Proxmox networks, and manage IP address pools (IPAM) so CMP can allocate and track IPs for customer VMs.

When a customer creates a VM (or similar compute resource) on Proxmox VE, CMP must choose which node receives that workload.

Before StackConsole / CMP can provision VMs on Proxmox, prepare at least one cloud-init-ready template on the Proxmox node.

Map Proxmox compute into CMP rate card packages so customers can purchase and provision resources.

This section covers integrating CMP with Proxmox VE as a compute orchestrator.

Explore the features currently available through StackConsole CMP, understand the infrastructure prerequisites, and identify limitations and additional configuration requirements.

This page is the Proxmox VE onboarding checklist for StackConsole / CMP. Complete the common prerequisites and confirm hosting topology as well.

When CMP creates or cancels an IP subscription on a Proxmox network imported in CMP — not how to set the rate-card price.

Before customers can provision VMs from CMP on Proxmox VE, prepare at least one cloud-init-ready VM template on Proxmox.

Unit Pricing defines the per-unit monthly rates CMP uses when customers provision Proxmox resources through custom packages — they enter vCPU, memory, storage (and IP where applicable) instead of selecting a predefined package tier.

What is under development for an upcoming CMP version versus what remains on the longer roadmap.

VM packages define the compute customers select when creating instances on Proxmox: vCPU, memory, OS family, and (depending on override disk) root disk size and pricing.

VM Snapshot packages define how CMP bills VM (instance) snapshots on Proxmox (VM_SNAPSHOT). Pricing is hourly per GB based on snapshot size.

Volumes packages define disk size, storage category, and storage pricing on the rate card. On Proxmox they are used when: