Hyper-v virtual machine management templates – HP Matrix Operating Environment Software User Manual
Page 38
Insight Control virtual machine management templates
Matrix infrastructure orchestration uses VMware templates as deployment targets for ESX. For
information about creating VMware templates, see the VMware documentation at
.
NOTE:
VM template-based provisioning is not available for Integrity VM.
To create virtual machine management templates from virtual machines, use Systems Insight Manager
to do the following:
1.
Power off the virtual machine to be used in the virtual machine management template. It is
good practice to cleanly power off the virtual machine by accessing the virtual machine and
performing an operating system shutdown rather than using a hypervisor power off command.
If the virtual machine is in a suspended state when used to create the template, provisioning
will fail during customization with the error message VM must be powered off for
customization
.
2.
Click Deploy
→Virtual Machine→Templates→Create Virtual Machine Template. The Step 1:
Select Source Virtual Machine screen appears.
3.
Select a virtual machine from the list, and then click Next. The Step 2: Select VM Template
Repository Host screen appears.
4.
Select the host for the new virtual machine management template, and then click Next. The
Step 3: Specify the Template Name and select VM Template Repository Folder screen appears.
5.
In Template Name, enter a name for the template and specify a location for the template.
6.
To store the virtual machine management template, in the target folder, select Browse and
select a virtual machine host datastore folder, or click Next to select the default choice.
7.
Click Next. The Step 4: Confirm Details screen appears.
8.
Click Run Now. The task results appear.
Insight Control virtual machine management template creation might take from 5 minutes up
to 30 minutes to complete.
The resulting ESX VM template is discovered and displayed in the Software tab in the infrastructure
orchestration console, and can be selected as the software when configuring a server group in an
IO template in infrastructure orchestration designer.
When configuring an IO template and specifying a VM template as the software, changes made
to the VM template after the IO template is created are not reflected in the IO template. If a service
is created from that (outdated) IO template, the service uses information from the updated VM
template. Therefore, the resulting service may not reflect the values in the IO template. To avoid
this issue, if the VM template is changed, create a new IO template and select the updated VM
template as the software before deploying the service.
NOTE:
Use ESX and Hyper-V VM templates with boot disks only. VM templates that have data
disks defined do not appear in the infrastructure orchestration software inventory so cannot be
used in infrastructure orchestration templates.
Data disks can be added to a virtual server by defining them in an infrastructure orchestration
template.
Hyper-V virtual machine management templates
A Hyper-V VM template is not automatically discovered. Hyper-V templates must be imported into
HP Insight Control virtual machine management before they appear in IO on the Software tab as
VM templates.
Matrix infrastructure orchestration uses a Hyper-V virtual machine as the source material for a
Hyper-V virtual machine management template without any additional steps. However, to provision
logical servers, deploy the Hyper-V virtual machine host in a Windows cluster.
38
Installation and configuration