|Manuals

Model Versioning

VDI/DaaS model versioning in Cloud Manager lets you maintain separate versions of a model — Production, Testing, and Staging — and progress through them in a controlled, reversible workflow. Versioning applies to VDI/DaaS Models; Managed VMs and Kubernetes Models use a single configuration.

For step-by-step instructions on creating and promoting versions, see Update a Model’s Version.

Version States

Each version of a model has one of three states.

Testing. A sandbox version for experimenting with new configurations, template updates, or feature changes without affecting users.

Staging. A pre-production validation state that mirrors the upcoming Production configuration.

Production. The live version that end users interact with through Access Profiles.

A model may have several versions in different states at the same time — for example, one Production version serving end users while a Testing version receives in-progress edits.

Version Promotion Workflow

   Create new version (copy of Production)
                 │
                 ▼
            Testing ──promote──▶ Staging ──promote──▶ Production
              ▲                                          │
              └────── rollback via export/import ────────┘

Rollback is performed by re-importing a previously exported version. See Export and Import Models.

Warning

Promoting a version overwrites the target. For example, promoting Testing to Staging replaces the current Staging version. Always export the version you are about to overwrite if you need to keep a backup.

Impact on active instances.

Changing the Production version affects all future deployments from the model. Instances already running continue operating under the configuration they were provisioned with. New instances deployed after the version change use the updated Production configuration.

What’s Next

See Also