My OS Template

My OS Template allows you to create reusable Virtual Machine system images from root disk snapshots.

An OS Template captures the operating system and system-level configuration of a Virtual Machine at a specific point in time, enabling you to quickly deploy new VMs with the same baseline setup.

This feature is designed for consistency, speed, and standardization, not for backups.

What Is an OS Template?

An OS Template is a reusable system image created from a root disk snapshot.

It represents:

• The operating system
• Installed packages and dependencies
• System configuration at the disk level

What OS Templates Are (and Are Not)

OS Templates Are Used For

• Deploy multiple VMs with identical system configurations
• Create golden images for production environments
• Speed up VM provisioning
• Reduce configuration drift

OS Templates Are NOT

• Backups
• Live VM states
• Data recovery tools for user data
• Replacements for snapshot schedules

For data protection and recovery, always use snapshots and backups.

How OS Templates Work in CloudRaya

In CloudRaya, OS Templates are derived directly from root disk snapshots.

The workflow is:

Virtual Machine
   ↓
Root Disk Snapshot
   ↓
Convert to OS Template
   ↓
Reusable VM Deployment Image

Important characteristics:

• OS Templates are created only from root disk snapshots
• They are not live system images
• They are stored independently from the original VM
• They can be reused multiple times to create new VMs

Creating an OS Template

OS Templates are created by converting an existing root disk snapshot.

High-level process:

1. Take a snapshot of a Virtual Machine root disk
2. Select Convert to OS Template
3. The template becomes available in Storage → My OS Template

Once created, the OS Template can be used to launch new Virtual Machines.

Using an OS Template to Create a Virtual Machine

When you create a new Virtual Machine using an OS Template:

• The region is automatically pre-selected
  (based on where the snapshot was created)

• The OS Template is pre-selected in the VM creation flow

• You continue configuring:

  • VM specifications
  • Networking
  • SSH keys
  • Optional settings

This ensures compatibility and avoids cross-region inconsistencies.
OS Templates behave like system images, not like attached disks.

OS Template Lifecycle

OS Templates have their own lifecycle, independent of the original VM.

What Happens When the Original VM Is Deleted?

• Deleting the VM does not delete:
  • Snapshots
  • OS Templates created from those snapshots
• OS Templates must be managed and deleted manually

This allows long-term reuse even after the source VM is gone.

Limitations and Notes

• Only root disk snapshots can be converted into OS Templates
• OS Templates cannot be attached as storage volumes
• OS Templates are region-specific
• OS Templates incur storage cost while retained
• Changes to a running VM do not affect existing OS Templates

Best Practices

Recommended usage patterns:

• Create OS Templates from:
  • Clean, fully updated systems
  • Hardened baseline configurations
• Use OS Templates for:
  • Production VM standardization
  • Repeated deployments
• Avoid:
  • Using OS Templates as backup mechanisms
  • Creating templates from unstable or temporary VMs
• Periodically review and remove unused OS Templates to control cost

Related Guides

• Learn how snapshots work and how they are used for data protection and recovery.

  📄 Backups and Snapshots

• Understand root disks, additional storage, and snapshot behavior.

  📄 VM Storage & Volumes

• Deploy a new VM using an OS Template or standard OS image.

  📄 Create a Virtual Machine