Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Active System Manager Release 8.1.1 Installation Guide

PDF

Customizing Virtual Machine Templates or Virtual Machines for VMware or Hyper-V

ASM can clone existing virtual machines and virtual machine templates in vCenter, or virtual machine templates in Hyper-V. The source virtual machines and virtual machine templates must be customized according to the instructions provided in this section. After customization, you must shut down the virtual machine and you cannot restart the virtual machine. For VMware virtual machines or virtual machine templates, cloning is supported as long as you are cloning within the same datacenter. For SCVMM the virtual machine templates must exist in the SCVMM library. Cloning virtual machines directly is not currently supported for Hyper-V.
  • NOTE: After customization, if you restart the virtual machines, the virtual machine will no longer be valid for cloning, and in that case, the verification file must be deleted. See later in this section about deleting the verification file.

The following customization is required only for VMware virtual machines:

Install VMWare Tools on the virtual machine:
  • If the virtual machine being used does not have a DVD drive, you must add one. To do this, edit the settings of the virtual machine and add a DVD drive through your VMware management console.

  • Once a DVD drive is available, right-click the virtual machine and select Guest-> Install/Upgrade VMware Tools. This will mount the media for VMware tools.

  • Log into the operating system of the virtual machine and run the VMware tools installer within the OS running on the virtual machine. See VMware documentation for further information on installing VMware tools.

The following customization is required for both VMWare and Hyper-V virtual machine

Install the puppet agent on the virtual machine:

  • If the virtual machine being used was successfully created by ASM, the puppet agent will already be installed.

  • To install the puppet agent on the virtual machine, copy the puppet agent install files to the virtual machine. The puppet agent is available on the ASM appliance for both Windows and Linux

    in /var/lib/razor/repo-store directory. If the virtual machine being customized has network access to the ASM appliance, you can connect to this same directory as a network share directory using the address: \\<ASM appliance hostname or IP>\razor\puppet-agent .

    Depending on your operating system, the installer may require additional packages (.rpms) which are dependencies and you must install it first. If the installer reports such dependencies, use the correct method for your operating system to find and install the dependencies, and then retry installation of the puppet agent.

    • NOTE: The puppet agent version should be greater than 3.0.0 and lower than 3.4
  • After you install the puppet agent, make sure the puppet agent service is enabled to run on system start.
    • For Windows virtual machines, this must be done by viewing the services and setting the puppet agent service to "automatic".

    • For Linux virtual machines, verify whether or not the puppet agent is enabled by running the following command and checking the value of "enable" is set to true:

    Puppet resource service puppet
    • If the service is not set to true as noted above, run the following puppet command as administrator:

puppet resource service puppet enable=true
  • Time must be synchronized between the ASM appliance and the virtual machine being cloned to ensure proper check in upon completion of cloning. Make sure NTP is configured on the virtual machine. Follow the appropriate instructions for your operating system to synchronize the virtual machine with an NTP server.

  • Make sure the ASM appliance hostname "dellasm" can be resolved by using DNS. Either add the appropriate CNAME record in DNS* or add the appropriate host entries to "/etc/hosts" in Linux or "C:\windows\system32\driver\etc\hosts" in Windows.

  • Configure the puppet.conf file to use "dellasm" as a server. To configure the puppet.conf file, perform the following:

    • Identify the location of the puppet.conf file. To do this, run the following command as "administrator" in Windows or "root" in Linux which will display the directory of the puppet.conf file.

      puppet config print config
    • Open the puppet.conf file by using a text editor and add the line "server = dellasm" to the [main],[master], and [agent] section. If any of these sections does not exist, create them. A sample resulting puppet.conf file may look similar to the following:
      [main]
                                                   server=dellasm
                                                   [master]
                                                   server=dellasm
                                                   [agent]
                                                   server=dellasm 
                                                
      • NOTE: Additional lines may be present in the puppet.conf file for your system. It is not necessary to delete any information from this file. You just need to ensure the previously noted section is present in the file.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\