After you install the guest agent and software bootstrap agent on your reference machine, you disable SELinux to ensure your template supports the specific implementation of MySQL used in the Dukes Bank sample application. You turn your reference machine into a template that you can use to provision the Dukes Bank vSphere sample application.

About this task

After you convert your reference machine to a template, you cannot edit or power on the template unless you convert it back to a virtual machine.

Procedure

  1. Log in to your reference machine as the root user.
    1. Edit your /etc/selinux/config file to disable SELinux.
      SELINUX=disabled

      If you do not disable SELinux, the MySQL software component of the Duke's Bank Sample application might not work as expected.

    2. Remove udev persistence rules.
      /bin/rm -f /etc/udev/rules.d/70*
    3. Enable machines cloned from this template to have their own unique identifiers.
      /bin/sed -i '/^\(HWADDR\|UUID\)=/d'
      /etc/sysconfig/network-scripts/ifcfg-eth0
    4. If you rebooted or reconfigured the reference machine after installing the software bootstrap agent, reset the agent.
      /opt/vmware-appdirector/agent-bootstrap/agent_reset.sh
    5. Power down the machine.
      shutdown -h now
  2. Log in to the vSphere Web Client as an administrator.
  3. Right-click your reference machine and select Edit Settings.
  4. Enter dukes_bank_template in the VM Name text box.
  5. If your reference machine has a CentOS guest operating system, select Red Hat Enterprise Linux 6 (64-bit) from the Guest OS Version drop-down menu.

    If you select CentOS, your template and customization specification might not work as expected.

  6. Click OK.
  7. Right-click your reference machine in the vSphere Web Client and select Template > Convert to Template.

Results

vCenter Server marks your dukes_bank_template reference machine as a template and displays the task in the Recent Tasks pane. If you have already brought your vSphere environment under vRealize Automation management, your template is discovered during the next automated data collection. If you have not configured your vRealize Automation yet, the template is collected during that process.