Releasing A Virtual Machine From Usage; Managing Virtual Machine Templates - Novell PLATESPIN ORCHESTRATE 2.0.2 - VIRTUAL MACHINE MANAGEMENT GUIDE 10-17-2009 Management Manual

Table of Contents

Advertisement

2.2.3 Releasing a Virtual Machine from Usage

When the demand and load on your data center decreases, the Orchestrate Server analyzes the
remaining resources and releases the most appropriate resource. If a VM meets the requirements of
the remaining job demands better than a physical machine, the physical machine is released before
the VM is released. This dynamic analysis allows you to make sure that the needs of your data
center are met.

2.2.4 Managing Virtual Machine Templates

A VM template is a special kind of VM that is not deployed separately. When the Orchestrate Server
needs a VM of the template's type to be used as a resource, it automatically clones a version of the
VM and uses that clone as the VM. You can change cloned VMs into instances of VMs instead of
clones.
Review the following tasks to manage VM templates:
"Making a Virtual Machine Instance into a Template" on page 27
"Changing a Virtual Machine Template Clone to an Instance" on page 27
Making a Virtual Machine Instance into a Template
1 In the Orchestrate Development Client, right-click the VM.
2 Select Create Template.
3 Name the template.
4 Specify a repository.
5 Specify a visible VM host.
6 Select a recommended host for the VMs to be launched on, if any are present.
7 Click OK.
When the clone of the template VM is provisioned, it appears as a sub-branch of the template's
location in the resources tree, as in the following Linux and Windows examples:
This clone functions as an instance of a VM and runs as though it were its own version with its own
MAC address and other unique identifiers. The UUID is the only new information that is
automatically generated for the clone. All the rest of the new information comes from autoprep,
including the MAC address if an asterisk (*) is placed in the Mac Address field in the Autoprep
Network Adapter section of the Info/Groups tab for the template (the default is a blank field,
meaning no MAC address is created), and if the Use Autoprep check box is enabled in the Create
VM from Template dialog box.
Changing a Virtual Machine Template Clone to an Instance
1 If you decide to keep a clone VM, go to the PlateSpin Orchestrate Development Client, right-
click it, and select Remove Template Dependency.
The Remove Template Dependency dialog box is displayed.
2 Click OK.
Managing Virtual Machines
27

Advertisement

Table of Contents
loading

This manual is also suitable for:

Platespin orchestrate 2.0.2 virtual machine

Table of Contents