67 docs tagged with "features"

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.

CMP is built on REST-based APIs. Use this page to enable API access, generate tokens, authenticate, and configure role-based permissions for integrations.

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.

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

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.

NoVNC / console proxy access from the CMP customer portal.

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.

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

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.

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.

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.

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.

CMP notification system for customer and admin alerts — email (and related channels), event-driven messages, and notification preferences.

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

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

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

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.

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

This section covers CMP-level capabilities that are not tied to a single orchestrator — APIs, notifications, store/marketplace, and other cross-cutting product features.

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

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.

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.

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.

CMP supports sending transactional SMS messages — including one-time passwords (OTP) for mobile verification during customer registration — through external SMS service providers.

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.

This documentation describes an improvement on the basic Products / Store feature. It is not yet rolled out to all deployments — you may find that some of these capabilities are not available on your CMP today. They will become available in upcoming updates.

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

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.

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

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

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.

This page has moved.

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

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

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

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.