12 docs tagged with "rate-cards"

Before customers can purchase Web Hosting plans or provision cPanel accounts, they must be registered in StackConsole CMP and assigned an active rate card containing Web Hosting packages.

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

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

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.

In StackConsole CMP, Web Hosting plans are commercial offerings that map directly to underlying WHM packages. This guide covers how to create CMP-compatible packages in WHM, understand critical naming constraints, and map packages to sellable plans and rate cards in CMP.

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.

Admin setup for CMP service contracts — rate card Yearly prices, Update Billing Rule fields, per-mode discounts, cancellation deadline, and a verification checklist.

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.

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

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.