48 docs tagged with "packages"

Questions tied to Apache CloudStack behaviour and how CMP uses ACS APIs. Feature guides: CloudStack features, Networks.

After zones and templates are configured, map CloudStack offerings to CMP rate card packages so customers can provision and purchase resources.

IP Address packages control how much public / network IPs cost on the rate card. The same package price is used for VM-create IPs, standalone IPs, and shared-network IPs (when billing is enabled on that network).

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.

CMP supports DNS domain billing — customers can be charged when they create a DNS domain, typically on an hourly or monthly cycle.

Free trials allow providers to offer selected resources to customers at no cost for a limited period. Customers can explore services and evaluate the platform before moving to paid usage.

Rate card package for customer-owned / account images (Glance), if billed in CMP.

CMP bills public / 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, as a standalone IP, or on a Shared Network.

Map floating IPs / public IP pools to CMP IP packages using externalnetworkid.

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.

ISO images allow cloud customers to boot virtual machines from custom installation media, live distributions, or diagnostic tools instead of pre-configured OS templates.

Kubernetes node packages define the compute plans customers select for control (master) nodes and worker nodes when creating or scaling a CloudStack Kubernetes cluster in CMP.

Map Magnum (or equivalent) container infra to CMP Kubernetes packages when enabled.

Load Balancer packages define how CMP bills customers for network-level load balancing in CloudStack. In CloudStack, load balancers operate at the network and public IP layer — the virtual router distributes traffic to backend VMs using load balancer rules.

Map Octavia (or equivalent) load balancers to CMP packages when enabled.

Network packages define how CMP bills Isolated and L2 guest networks. Each package maps to a CloudStack network offering for a Cloud Provider Setup and zone.

In CMP OpenStack deployments, network provisioning is non-billed. Neither private (tenant) networks nor shared public (external) networks incur a network infrastructure package charge.

Object Storage packages define the CEPH plans customers purchase in CMP — storage capacity, bucket limits, zone, storage category, and pricing.

Object Storage packages define the Impossible Cloud plans customers purchase in CMP — storage capacity, zone, storage category, and pricing.

After regions and images are configured, map OpenStack resources (flavors, networks, volumes, floating IPs, and so on) to CMP rate card packages so customers can provision and purchase.

ISO packages define how CMP bills customers for customer-owned ISO images stored in CloudStack Secondary Storage. Customers use these ISOs to boot virtual machines from custom install media or diagnostics rather than pre-built templates.

Before offering custom ISO registration to customers, ensure your CloudStack network, Secondary Storage VM (SSVM), and CMP settings are properly configured.

CMP uses consistent formulas to derive all billing cycle prices from a single base value. Define one price and the others are calculated automatically.

This page is the rate card package entry for Products under CloudStack packages.

Non-automated or store products tied to the OpenStack rate card (if used).

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

Rate cards define what customers can buy and how much they pay. A rate card is a pricing catalogue — it contains packages (Virtual Machine, Volumes, IP Address, and so on) with orchestrator mappings and billing rates.

When CMP creates or cancels an IP subscription on a CloudStack Shared / VLAN network — not how to set the rate-card price.

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

Custom Template packages define how CMP bills customers for customer-owned templates (ACCOUNT_TEMPLATE) stored under the My Template service. This is separate from admin-prepared OS templates used for standard VM provisioning.

Unit Pricing defines the per-unit monthly rates CMP uses to calculate bills when customers provision resources through custom packages — configurations they enter manually instead of selecting a predefined package tier.

Per-unit rates used with custom OpenStack packages (same pattern as other orchestrators).

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.

After connecting Veeam, configure how customers buy Veeam capacity in CMP:

Virtual Machine (VM) packages define the compute bundles (vCPU and RAM) that customers select when provisioning instances. Each predefined package in CMP maps to one CloudStack compute offering through the Select Offering field.

Map Nova flavors to CMP Virtual Machine packages so customers can provision compute from the rate card.

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.

Virtual Router Packages define how CMP provisions, bills, and accounts for Neutron routers in OpenStack. A CMP virtual router maps to an OpenStack Neutron router. The package's External Network Id is used as the router's external gateway network.

Virtual Router / VPC packages define the VPC tiers customers select when creating a Virtual Private Cloud in CMP. Each package maps directly to CloudStack offerings:

VM Autoscale packages define an optional charge for the Auto Scaling engine itself. They are separate from billing for VMs, load balancers, IP addresses, and other resources, which use their own packages.

VM Backup packages define how CMP bills customers for virtual machine backups (BACKUP). When a customer creates or retains a VM backup, CMP charges based on the backup size in GB and the per-GB hourly rate configured in this package.

Override root disk, free OS disk, scheduled stop, and related packaging choices. CloudStack offering mapping: Virtual Machine packages.

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 map CloudStack disk offerings to CMP storage tiers. They are used when customers:

Volume Packages define CMP block-storage tiers for OpenStack Cinder. They are used when customers select a root-disk size during VM creation, purchase additional block-storage volumes, and select boot/root storage for Kubernetes nodes when disk override is enabled.

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

Volume Snapshot packages define how CMP bills customers for block storage volume snapshots (BS_SNAPSHOT). When a customer takes a snapshot of a root or data volume, CMP charges based on the current snapshot size and the per-GB hourly rate configured in this package.

Billing and package setup for Cinder volume snapshots.