81 docs tagged with "cloudstack"

Admins can create version-specific user guides that end customers see on the cluster Access tab — for example how to use the CLI, open the dashboard, and run common commands.

How end users (and admins verifying a cluster) open the Kubernetes Dashboard with kubectl and a kubeconfig from CMP.

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

When Enable Provider Backup is No, CMP does not run a separate backup engine. It automates scheduled CloudStack volume snapshots on the VM root disk and exposes them in CMP as the VM backup and recovery mechanism — schedule, retain, restore, and bill via the VM Backup package.

CloudStack horizontal auto-scaling in CMP — practical architecture considerations and how customers create autoscale configurations.

VM backup in CMP for CloudStack is orchestrator-integrated — customers schedule, run, and restore backups from the VM in CMP. No backup agents and no separate backup dashboard for the customer.

CMP offers two different backup models. They are easy to confuse because both can involve Veeam — but the customer experience is completely different.

Concept-only answers. Full comparison: Backup and Recovery.

Instances Backup Schedules are CMP policies that automatically create VM backups on a recurring interval. Each run produces a backup object visible under Virtual Machines → Backups (and on the VM Backups tab).

CMP bills outgoing network bandwidth as a usage-based service. On CloudStack, usage is collected at the network level (Isolated networks and, optionally, VPC) — not per VM.

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.

When CloudStack Backup and Recovery (B&R) is configured, CMP uses CloudStack B&R APIs to manage VM backups. The customer schedules, runs, and restores from the VM in CMP — no agents and no manual backup setup on the customer side.

CloudStack supports horizontal auto-scaling: instead of increasing CPU/RAM on an existing VM (vertical scale), it provisions additional VM instances when defined thresholds are met (CPU, network traffic, custom metrics, and similar).

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

This page has moved to Orchestrator Features → CloudStack → Backup.

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).

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.

This page is in progress. Content, create-form fields, and screenshots will be expanded as CMP Autoscale documentation is completed.

Customers can create a My Template from an existing virtual machine’s root volume. This is the main way to build a golden image for Autoscaling and for repeatable app deployments.

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.

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.

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 images allow cloud customers to boot virtual machines from custom installation media, live distributions, or diagnostic tools instead of pre-configured OS templates.

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 network packages (billing controlled globally by enablenetworkbilling).

Managed Kubernetes (CKS) in CMP for Apache CloudStack 4.20+, with admin panel behaviour from 4.21.0 onward: separate control and worker plans, resource-based billing, and cluster management tabs for VMs, volumes, load balancers, and access.

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.

An L2 Network in Apache CloudStack provides Layer 2 connectivity only (switching / VLAN). CloudStack attaches VMs to the VLAN or broadcast domain and does not deploy a virtual router for Layer 3 services.

This page separates what CMP admins configure in CMP from behaviour and limits defined by Apache CloudStack on the virtual router. Customers enable Remote Access VPN in CMP; underlying VPN service, global tuning, and documented limits come from CloudStack.

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.

The Backups screen lists VM backup copies created from a backup schedule — either by the timer or by manual trigger (Run now).

Marketplace apps are VM templates with pre-installed applications. The service provider prepares the image (OS + application) so end users can deploy a ready-to-use app without installing software manually.

StackConsole / CMP shows VM performance charts using monitoring data from Apache CloudStack only. You do not need to deploy a separate monitoring platform such as Zabbix, Prometheus, Grafana, or similar for this CMP monitoring view.

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

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.

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.

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 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.

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

This page is the rate card package entry for Products under CloudStack 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.

Remote Access VPN (Road Warrior) lets an individual user connect from a laptop or PC over the internet to private VMs on a VPC or Isolated network — without exposing VM private IPs to the public internet.

CMP uses its own scheduler to run recurring jobs — separate from CloudStack cron or backup-provider schedules. Customers define a schedule policy (frequency, timezone, retention); CMP executes it and stores the results as backups or snapshots.

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 Network, it is not dedicated to a single tenant’s private router model in the same way.

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

This section outlines workflows and details based on Apache CloudStack documentation and general Site-to-Site VPN practice. It has not been practically reviewed end-to-end in CMP — validate steps, field behaviour, and tunnel setup against your CloudStack version and customer firewall before production use.

This page has moved to Orchestrator Features → CloudStack → Backup.

Volume Snapshot Schedules are CMP policies that automatically create block storage volume snapshots on a recurring interval. Each run produces a snapshot under Virtual Machines → Snapshots → Volumes Snapshot.

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

Marketplace Apps usually rely on an administrator startup script on the template. Customers may also enter their own startup script at deploy time. Both are combined into UserData sent to CloudStack, so size limits must be aligned.

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.

The Import Virtual Machine feature lets administrators onboard existing virtual machines from Apache CloudStack into Stack Console (CMP).

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 in CMP for CloudStack — create and manage account-owned templates, use them when provisioning instances, and (when enabled) bill storage via Custom Template packages.

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.

Create, manage, start/stop, and delete instances on CloudStack through CMP. Feature pages for Change Plan, downgrade, and related VM behaviour live in this section.

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.

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.

This page has moved.

VM Downgrade lets a customer move an existing VM to a lower compute plan (CPU / memory) through Change Plan.

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.

A static route tells your VPC where to send traffic for a remote network. Customers manage VPC-level static routes from the VPC details page in CMP.

Workflows on this page follow CloudStack documentation and general Site-to-Site VPN practice. Not practically reviewed end-to-end in CMP — see Site-to-Site VPN.

Field details on this page follow CloudStack documentation and general Site-to-Site VPN practice. Not practically reviewed end-to-end in CMP — see Site-to-Site VPN.

Workflows on this page follow CloudStack documentation and general Site-to-Site VPN practice. Not practically reviewed end-to-end in CMP — see Site-to-Site VPN.

VPN Users provide username/password credentials for Remote Access VPN. Users connect with an L2TP/IPsec client to the Source NAT public IP (VPC or Isolated network) where Remote Access VPN is enabled.

End-to-end setup for personal PC → private VM using Remote Access VPN. The same model applies to VPC and Isolated networks — enable VPN on the Source NAT public IP, create a VPN User, configure an L2TP/IPsec client.