Skip to main content

Templates

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.

A properly configured template ensures that password management, SSH key injection, root disk scaling, startup scripts, and other CMP features work as expected.

Before you begin

Complete Connecting CMP to CloudStack through Wizard Step 4 before configuring templates in CMP. Templates must exist in CloudStack and be marked Public and Featured before they appear during CMP setup.

Pages in this section​

Template workflow​

The overall template workflow consists of the following steps:

  1. Prepare and validate the template at the CloudStack level.
  2. Register the template in CloudStack with the required options (Public, Featured, password-enabled, and so on).
  3. Re-configure the template manually in CMP (during Cloud Provider setup or from Settings → Orchestrator → Templates after setup).
  4. Configure the template within CMP (OS, version, password method, compute category, and related fields).
  5. Make the template available for customer VM deployments in the selected zone.
No self-service Sync option

Template inventory in CMP is not updated automatically when CloudStack changes. CMP does not provide a Sync button for templates. After any add, modify, or remove in CloudStack, an administrator must re-configure templates manually in CMP.

Quick compatibility checklist​

RequirementRequiredDescription
Password enabledYesRequired for CloudStack password management via UserData.
SSH enabledYesRequired for SSH key injection and secure access.
Startup script enabledYesAllows UserData and initialization scripts to run at first boot.
Scalable root diskYesRoot disk size must match the customer-selected package at provisioning time.
Public & FeaturedYesCloudStack templates must be Public and Featured to appear in CMP during configuration.

See Preparing CMP-Compatible Templates for the full validation checklist.

Frequently asked questions​

Can I create or modify templates directly in CloudStack?​

Yes. Templates can be created or modified directly in CloudStack. However, CMP is not updated automatically — an administrator must re-configure templates manually in CMP after any orchestrator-side change.

When do I need to re-configure templates in CMP?​

Whenever templates are added, modified, or removed in CloudStack. CMP does not offer a self-service Sync option — admins need to manually update those changes at CMP.

Why are templates configured separately for each zone?​

CMP manages templates independently for every Cloud Provider Setup and zone. Even if CloudStack shares a template across multiple zones, CMP requires a separate configuration entry for each zone.

Why do password-enabled templates fail on L2 networks?​

L2 networks and password-enabled templates

Apache CloudStack L2 networks do not support UserData. Password-enabled templates rely on UserData, so they cannot be deployed on L2 networks. Use a non-password-enabled template for L2 provisioning.