148 docs tagged with "orchestrator"

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.

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.

Virtual machine backup is available for Proxmox VE in CMP. Customers and admins can use Proxmox backups through CMP for VMs on the connected provider.

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.

CMP bills outgoing network bandwidth as a usage-based service. On OpenStack, CMP implements VM-level bandwidth billing using Gnocchi metrics (network.outgoing.bytes on the VM’s network interface).

After an object storage service is active, customers create buckets and manage objects (files) through CMP and S3-compatible APIs.

After an object storage service is active, customers create buckets and manage objects (files) through CMP and S3-compatible APIs.

This section covers integrating CMP with CEPH as a standalone S3-compatible object storage provider.

Feature documentation for CEPH object storage in CMP — customer and admin capabilities after the orchestrator is connected.

When does CMP register a customer on CloudStack?

When a customer is registered in CMP (admin onboarding or self-registration, depending on your payment mode), CMP registers them in OpenStack using the admin connector, then switches to the customer's own credentials for all later API calls.

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

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.

After a Glance image is ready in OpenStack, map it in CMP as a template entry so customers can select it when creating VMs. The CMP UI uses the same Add Template form as other orchestrators; most fields match Configuring Templates in CMP (CloudStack).

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 connecting CMP to a CEPH cluster for object storage — Dashboard API credentials, S3 endpoints, zone mapping, and storage settings.

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

Connect CMP to Impossible Cloud for object storage — Partner API credentials, ICMC (V1) endpoint, S3 region mapping, storage settings, and rate cards.

Connect CMP to your OpenStack-based cloud so CMP can authenticate (Keystone) and call Nova, Glance, Neutron, Cinder, and related APIs.

This guide walks through connecting CMP to a PowerDNS DNS backend so customers can manage DNS domains through the portal.

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

Connect CMP to Veeam Service Provider Console (VSPC) so Stack Console can create companies, assign quotas, and deliver credentials.

NoVNC / console proxy access from the CMP customer portal.

Requirements so customers can open the VM console from CMP (typically noVNC via Nova).

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.

End customers manage DNS domains and records from the customer portal after Connecting CMP to PowerDNS is complete.

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

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

OpenStack Glance images map to CMP templates (same Add Template UI as CloudStack). Prepare images in OpenStack, then configure them per zone in CMP.

This section covers integrating CMP with Impossible Cloud as a standalone S3-compatible object storage provider.

Feature documentation for Impossible Cloud object storage in CMP — customer and admin capabilities after the provider is connected.

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.

Public IP acquisition, association, and billing behaviour.

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.

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.

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

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.

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

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

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.

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

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.

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.

Customers create and manage CEPH-backed object storage services in CMP.

Customers create and manage Impossible Cloud-backed object storage services in CMP.

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.

This section covers integrating CMP with OpenNebula as a compute orchestrator.

Feature documentation for OpenNebula in CMP — customer and admin capabilities after the orchestrator is connected.

OpenStack is a supported compute orchestrator in CMP. This section covers setup — connecting CMP to OpenStack through packages, quotas, storage, and related configuration.

Feature documentation for OpenStack in CMP — what the OpenStack adapter supports today, what is on the roadmap, and links to setup / package docs after the orchestrator is connected.

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.

This section documents product features customers and admins use for each connected orchestrator — VMs, networks, storage, backups, and related capabilities in CMP.

Questions about how CMP works with a connected cloud (Virtual Machines, networks, passwords, zones, and similar).

After completing the common prerequisites, provide orchestrator-specific access and configuration. Each orchestrator has its own credentials, connectivity, and setup checkpoints.

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.

This section covers integrating CMP with PowerDNS for DNS-as-a-Service.

Feature documentation for PowerDNS in CMP — customer and admin capabilities after the orchestrator is connected.

Before a Glance image can be used for virtual machine provisioning through StackConsole CMP, prepare it correctly in OpenStack and then register it in CMP.

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 StackConsole / CMP can provision VMs on Proxmox, prepare at least one cloud-init-ready template on the Proxmox node.

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.

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

How CMP uses OpenStack projects and credentials for the cloud connector and for each customer.

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.

Feature documentation for Proxmox VE in CMP — what customers and admins can use after Proxmox setup is complete.

In OpenStack environments, public internet connectivity is delivered through shared external Neutron networks. Cloud providers configure these public networks in OpenStack and sync them to CMP, making them immediately accessible to all customer projects in that region.

CMP customer projects map one-to-one to OpenStack projects. Quota can be enforced in CMP only, or synced so OpenStack project limits follow CMP.

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.

After OpenStack is connected in CMP, map each customer-facing zone to an OpenStack region (and optionally an availability zone) before customers can provision in that location.

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.

When CMP creates or cancels an IP subscription on a Proxmox network imported in CMP — 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.

OpenStack snapshot and backup options for CMP (Cinder volume snapshots, image snapshots, and any backup service your cloud exposes).

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.

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.

Storage settings map OpenStack Cinder volume types to CMP storage categories (e.g. SSD Storage (NVMe), SSD Storage (SSD), Standard HDD). This mapping allows customers to choose storage tiers when deploying virtual machines, purchasing additional block storage volumes, or provisioning Kubernetes clusters.

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.

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

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

This section covers integrating CMP with Veeam Service Provider Console (VSPC) so Stack Console can automate company (customer) account creation, credentials, quotas, and plan changes.

Feature documentation for Veeam Service Provider Console (VSPC) in CMP — how customers consume Veeam plans after Veeam setup is complete.

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

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.

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.

This page has moved.

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

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

Feature documentation for VMware vSphere in CMP — customer and admin capabilities after the orchestrator is connected.

This section covers integrating CMP with VMware vSphere as a compute orchestrator.

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

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.