Phase 3: Templatize

After a successful build, templatizing saves the current state of all your VMs as a reusable template. Students deploy this template, and each deployment gets a fresh copy of the templated VMs.

The build is ready to templatize when the Create Machine Templates button appears in the top-right of the canvas. That means every play finished with no errors.

Note

This phase is meant for a build that finished with no errors. If a build ends with errors, you can still click Templatize Anyway. A Templatize Errored Build? warning tells you how many machines failed, because templates from that build are likely incomplete. For a clean template, fix the errors first, then Redeploy.

What Templatizing Does

• Snapshots every VM in its current state
• Packages them as a template that can be deployed repeatedly
• Enables the Publish phase (you can’t publish without a template)

Each time a student deploys your scenario, they get a new copy of these templated VMs. Your original build stays as it was.