Deployment Guide

4
Customizing Virtual Machine Templates
for VMware and Hyper-V
For ASM virtual machine (VM) cloning to work in conjunction with application components, you must
customize the virtual machine and virtual machine templates, install the puppet agent, and then install
the appropriate startup scripts.
Customizing Virtual Machine Templates or Virtual
Machines for VMware or Hyper-V
ASM can clone existing virtual machines and virtual machine templates in vCenter as long as they exist in
the same vCenter datacenter. The source virtual machines and virtual machine templates must be
customized according to the instructions provided in the section. After customization, you must shut
down the virtual machine and you cannot restart the virtual machine. You can clone virtual machine
templates that exist in the library for SCVMM by using ASM. However, the source virtual machine
templates are must be created according to the instructions provided in the section.
NOTE:
After customization, if you restart the virtual machines, the template will no longer valid for
cloning, and in that case, the verification file must be deleted. See later in this section about deleting
the verification file.
To customize VMware virtual machines and virtual machine templates, you must install the following
components:
For VMware tools: If ASM has deployed the virtual machine being used for customizing the virtual
machine for cloning, you must add a DVD drive to install VMware tools. In this case, the puppet agent
is already installed on the virtual machine.
Additional components that need to be included in virtual machine and virtual machine templates are
same for both Hyper-V and VMware:
Puppet certificate name scripts – You can find the puppet certificate name script in /opt/asm-
deployer/scripts on the ASM appliance. You can move the file to /var/lib/razor/repo-store and access
it through the network share on the appliance by the following instruction:
On a windows virtual machine, you must copy the script to “C:\”
On a Linux virtual machine, you must copy these scripts to /usr/local/bin.
Verify wheather or not the permissions are set on these scripts to at least read and execute.
run the command to verify:
chmod 755 /usr/local/bin/puppet_certname.sh
chmod 755 /usr/local/bin/puppet_certname.rb
Puppet Agent — You must install the puppet agent on the virtual machine. The puppet agent is
available on the appliance for both Windows and Linux in /var/lib/razor/repo-store directory. If the
virtual machine being customized and that has access to the ASM appliance, and then you can
26