Virtual Machine Templates

A cloud template is a preconfigured instance model created directly on a Cloud Provider (e.g. GCP). These templates define the hardware and software characteristics (OS, GPU, etc.) of a VM that will be automatically deployed via Reemo.

Note

When a template is created in Reemo, it is disabled by default and must be explicitly enabled by an instance administrator.

The standard process is as follows:

  1. The administrator configures their cloud provider in Reemo (e.g. adds GCP API keys).

  2. They create an instance template directly on the provider (e.g. GCP).

  3. They declare it in Reemo, linking it to the configured provider.

  4. Once enabled, Reemo can automatically deploy workstations based on this template.

This allows immediate access to remote desktops (VMs) through the Reemo protocol.

Cloud Templates List

The page lists all cloud templates available in the instance. Each template includes key information:

  • Template name (e.g. GPU Workstation)

  • Cloud provider type (e.g. GCP)

  • Visibility (PRIVATE or PUBLIC)

  • Status (ENABLED or DISABLED)

../../_static/images/instance/cloud-templates/instance_template_list.png

List of cloud templates available in the instance.

Creating a Cloud Template

When creating a new template, the administrator provides:

  • Name of the template (e.g. GPU Workstation).

  • Cloud provider type (e.g. GCP, AWS, Azure depending on configuration).

  • Visibility (PRIVATE or PUBLIC).

  • Optional SVG icon for visual identification.

  • Comments (e.g. associated GPU type).

  • Maximum number of VMs available for this template.

  • Option: limit the total number of deployable VMs with this model.

../../_static/images/instance/cloud-templates/instance_template_create.png

Form for creating a new cloud template.


For GCP specifically, an additional step is required:

  • Create an instance template on GCP.

  • Copy/paste the GCP template name into Reemo.

  • Select the operating system (Windows or Linux).

../../_static/images/instance/cloud-templates/instance_template_create_part2.png

GCP template configuration in Reemo.

Cloud Template Profile

Once created, each template has a profile page containing:

  • Provider type (e.g. GCP).

  • Creation date.

  • Visibility (PRIVATE or PUBLIC).

  • Status (ENABLED or DISABLED).

  • Comments (e.g. nvidia-tesla-p4-vws).

  • Maximum number of available VMs.

  • Detailed configuration: mapping of keys (e.g. templateName, os) to values.

../../_static/images/instance/cloud-templates/instance_template_profile.png

Detailed profile of a cloud template configured in Reemo.

Activation and Usage

  • By default, a newly added template is DISABLED.

  • To use it, the administrator must enable it manually.

  • Once enabled, Reemo can automatically deploy VMs on the associated provider (e.g. GCP).

Important

To use a Cloud Template, you must enable the Pool mode of a Group in an organization, then select the Cloud Provider and Cloud Template to deploy.

Private Cloud Template Association

Cloud Templates can be created in PUBLIC or PRIVATE mode.

  • In PUBLIC mode, all organizations have direct access.

  • In PRIVATE mode, templates must be explicitly associated with an organization before use.

This distinction allows controlled visibility and usage in multi-organization environments.

Association Management

From the Cloud Templates section of an organization, it is possible to associate a private Cloud Template available on a Cloud Provider.

../../_static/images/instance/cloud-templates/instance_orga_template_list_assigned.png

List of private Cloud Templates associated with the organization

Note

When a template is private, it will not be visible to organizations until it is assigned.

Associating a Template

Associating a private Cloud Template with an organization is done by selecting the Assign existing template menu. A dialog box then allows the template to be chosen.

../../_static/images/instance/cloud-templates/instance_orga_template_assign.png

Dialog for associating a private Cloud Template

Once associated, the template becomes available for the selected organization. It can then be used to deploy VMs via the Reemo interface. Private templates appear in the organization’s list. They can be removed (Unassign) at any time if necessary.

It is also possible to create a new Cloud Template directly from the organization context.


../../_static/images/instance/cloud-templates/instance_orga_template_new_menu.png

Menu for creating a template from an organization

Summary

  • With Cloud Templates you can centralize VM model management.

  • You can ensure reproducibility of deployments.

  • You can provide users with ready-to-use workstations, directly accessible through Reemo.

  • Public Cloud Templates are available to all organizations.

  • Private Cloud Templates require explicit association.