10 docs tagged with "templates"

Path: Settings → Orchestrator → Apps Marketplace

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.

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.

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.

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.

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.