32 docs tagged with "openstack"

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.

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

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.

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

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

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

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.

Map floating IPs / public IP pools to CMP IP packages using externalnetworkid.

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

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

In CMP OpenStack deployments, network provisioning is non-billed. Neither private (tenant) networks nor shared public (external) networks incur a network infrastructure package charge.

OpenStack-specific support questions will be collected here as they are validated.

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 page is the OpenStack onboarding checklist for StackConsole / CMP. Complete the common prerequisites and confirm hosting topology as well.

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.

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.

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.

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.

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

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.

Per-unit rates used with custom OpenStack packages (same pattern as other orchestrators).

Map Nova flavors to CMP Virtual Machine packages so customers can provision compute from the rate card.

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.

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

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.

Billing and package setup for Cinder volume snapshots.