Appendix-A_ VM Template Preparation (non-cloud-init)

Before You Begin

• Ensure VM (Template) has network connectivity to https://repo.skygrid.cloud/repo/ & Linux Repository

VMware vSphere

• Guest Customization: Create VMware Guest Customization with the exact same name of the VM Template Name for e.g. when HyperCloud™ Platform deploys a VM from the Template VMT-Win2k16x64 it will use the Guest Customization with the name VMT-Win2k16x64 if available to customize the provisioned VM.

Important Note: If the same vCenter Server will be used by more than 1 HyperCloud™ Platform then clone the same VM Template for each HyperCloud™ Platform. For example, use a Prefix for e.g. VMT-HCP-PROD-Win2k16x64 and VMT-HCP-QA-Win2k16x64 which will be used by the PROD and QA HyperCloud™ Platform respectively. Clone the Guest Customization too and ensure the name matches the VM Template name.

• Guest Customization Configuration:

  • Computer Name – Select use the Virtual Machine Name.

  • Network Type – DHCP

  • Windows Guest Customization:

    • Login Automatically as Administrator: 1

    • Run Once : Add the following in the Run once Command:

      Important Note: Update the HyperCloud_Platform_PROD_FQDN to HyperCloud_Platform_QA_FQDN for customizing VMs deployed from other HyperCloud_Platform(s).

• VM Tools: Latest VMware Tools must be installed on the VM Template or Guest Customization will fail. Refer VMware Supported OS for Guest Customization for supported Guest OS.

Microsoft Hyper-V Requirements

• Hyper-V Templates must be placed in a Cluster Shared Volume in the form of VHDX files.

• Ensure Hyper-V Integration Tools & service is installed and configured. Refer Hyper-V Integration Services and Supported Linux and FreeBSD virtual-machines

Important Note: For Linux VMs, remove older version of kernel and reboot the system

Open Virtualization (Ovirt) KVM Requirements

• Ovirt Guest Agent & tools must be installed as described in Ovirt Guest Agent and Tools

• Ensure VM Templates are in the same datacenter used in HyperCloud to configure the Availability Zone

VMware vCloud Director

• Ensure VM Tools is installed on vApp Templates.

Important Note: Only vApp Templates created in vCloud or imported from vCenter are supported. ISO and OVA formats not supported

• Ensure vApp Templates contain only 1 Tier (Single VM). Must be added to at least 1 Organization Catalog

Important Note: Use HyperCloud Blueprints to create multi-tier deployment.

• Guest OS must belong to list of supported OS in VMware Supported OS for Guest Customization

• When creating Template from an existing vApp, set vApp network = none

VM Template Preparation (Pre-Install HyperCloud Agent) (Recommended): This topic describes preinstalling the agent on VM Templates so HyperCloud does not need to install the agent on VMs deployed from the VM Template.
Important Note: Use this only if the VMs deployed using HyperCloud do not have internet access.

• Linux VM Templates (CentOS/Ubuntu/RHEL): Update the values for HCP_FQDN & run the following command on the Linux VM Template

  
  
  

• Windows VM Templates: Update HCP_FQDN & run the following in CMD Prompt

  
  Important Note: For Hyper-V & KVM - Run the following before shutting down the VM Template