47 docs tagged with "cloudstack"

This page covers the CloudStack-specific requirements needed before StackConsole can connect CMP to your Apache CloudStack environment. Complete the common prerequisites first.

When does CMP register a customer on CloudStack?

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

Apache CloudStack is CMP's primary supported compute orchestrator. This section covers the complete setup from connecting CMP to CloudStack through to snapshots and backups.

Feature documentation for Apache CloudStack in CMP — how compute, network, storage, and related services work for admins and customers after CloudStack setup is complete.

CloudStack 4.20 introduced a native backup and recovery framework. CMP integrates with this for setups running ACS 4.20 or later.

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

After a template has been created and validated at the orchestrator level, it must be re-configured manually in StackConsole CMP before it becomes available for customer VM provisioning.

After a zone has been created in CloudStack, it must be configured manually in StackConsole CMP before customers can provision resources in that datacenter region.

This guide walks through the complete process of connecting CMP to an

NoVNC / console proxy access from the CMP customer portal.

VM console access in CMP depends entirely on CloudStack's Console Proxy — a dedicated System VM (Console Proxy VM, or CPVM) that is separate from the virtual router and other system VMs. CMP does not host or proxy console traffic itself. When a customer opens a VM console in the CMP portal, CMP requests a console endpoint from CloudStack and redirects the customer to the CloudStack console proxy URL.

Global Resource Quota defines the default resource limits copied to every new customer account under a Cloud Provider setup. Customer-facing quota for CloudStack is managed entirely in CMP — not through CloudStack quota APIs.

IP Address packages control how public IP addresses are billed when customers provision VMs with public access or purchase standalone reserved IPs.

Public IP acquisition, association, and billing behaviour.

ISO image management in CMP for CloudStack — upload, attach, and bill customer ISOs when the ISO service is enabled for the platform.

ISO packages define how CMP bills customers for customer-owned ISO images stored in CMP. Customers use ISOs to boot VMs from custom install media instead of a pre-built OS template.

An Isolated Network in Apache CloudStack is a private guest network dedicated to a single account. It is not part of a VPC. CMP creates and manages isolated networks through network offerings, virtual routers, public IP behaviour, and optional network billing.

Managed Kubernetes clusters provisioned via CloudStack / CMP.

Kubernetes packages define managed cluster configurations (node size, count ranges) mapped to the orchestrator's K8s cluster template.

An L2 Network in CloudStack is a layer-2 guest network. It does not deploy a virtual router for L3 services the way isolated or VPC networks do.

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.

Network load balancer rules and CMP load balancer packages.

CloudStack network types available through CMP. Each type has its own guest network model, routing behaviour, and package requirements.

CMP manages quotas at the application level. Each connected orchestrator also enforces its own limits. The two systems are not synced automatically — admins must keep orchestrator limits equal to or greater than CMP account and project quotas.

Before a template can be used for virtual machine provisioning through StackConsole CMP, it must be prepared and registered correctly at the CloudStack level. This page describes the recommended template requirements and best practices for Apache CloudStack.

Configure Products in CMP under Settings → Billing Setup → Rate Cards → Default → Packages.

CloudStack has its own quota management system at domain, account, and project levels. CMP also has a separate quota engine — and the two systems do not share state.

A Shared Network in CloudStack is a guest network that can be used by multiple accounts within a zone (subject to CloudStack scope and admin configuration). Unlike isolated networks, it is not dedicated to a single tenant’s private router model in the same way.

This page covers the CMP automated snapshot/backup feature used with CloudStack versions before 4.20. For ACS 4.20+, see CloudStack Native Backup (v4.20+).

Volume snapshots and VM (instance) snapshots in CMP for CloudStack — create, manage, and restore snapshot points for disks and instances.

Storage settings map CloudStack disk offerings to CMP storage categories so customers can choose storage tiers (for example, SSD or NVMe) when creating VMs and volumes.

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.

Customer My Templates and template usage in CMP for CloudStack — create templates from VMs, manage account templates, and use them when provisioning instances.

Templates are the foundation for provisioning virtual machines through StackConsole CMP. This section explains how to prepare templates that are fully compatible with CMP and how to configure and manage them in CMP after they are registered in CloudStack.

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.

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.

Create, manage, start/stop, and delete instances on CloudStack through CMP.

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:

Autoscale groups and related template/package requirements.

Configure VM Autoscale packages in CMP under Settings → Billing Setup → Rate Cards → Default → Packages.

Virtual machine backups in CMP for CloudStack — create, schedule, retain, and restore VM backups, with billing via the VM Backup package (BACKUP).

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.

Root and data volumes, attach/detach, resize, and storage-category behaviour.

Volumes packages map CloudStack disk offerings to CMP storage tiers. They are used when customers:

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.

A VPC (Virtual Private Cloud) in Apache CloudStack is a private, isolated part of the cloud with its own virtual network topology. Customers create VPCs in CMP by selecting a VPC package that maps to CloudStack VPC Offering and VPC Network Offering values.