Versions Compared

Old Version 8

changes.mady.by.user Former user

Saved on

compared with

New Version 9

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Notes:

  • (1) Ensure Private Cloud Providers have a public NAT only to SaaS HyperCloudTM Portal IP Addresses provided by HyperGrid.

  • (2) Only needed if HyperCloudTM will install the HyperCloudTM Agent via SSH.

    • Ignore if Agent is pre-installed or installed on demand via cloud-init (Recommended) for VMware/Hyper-V/KVM Templates

VM Template Preparation

...

VM Template Preparation (non-cloud-init)

Note

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 as the VM Template Name.

      • Example: When HCP 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.(1)

  • 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:

c:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy bypass -Command "Invoke-WebRequest

https://repo.skygrid.cloud/snapshot/6.5.2/LATEST/agents/hcp_agent_install_windows.ps1 OutFile c:\hcp_agent_install_windows.ps1"

c:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy bypass -Command "c:\hcp_agent_install_windows.ps1

https://repo.skygrid.cloud/snapshot/6.3.1/LATEST/

AUTO_INSERT < HyperCloud_Platform_PROD_FQDN>_https://<HyperCloud_Platform_PROD_FQDN > 5671 docker.skip (2)

  • VM Tools:

    • The latest VMware Tools must be installed on the VM Template or Guest Customization will fail.

Info

Information

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. (3)

Info

Information

Refer Hyper-V Integration Services and Supported Linux and FreeBSD virtual-machines.

  • 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. (4)

    • Ensure vApp Templates contain only one Tier (Single VM). It must be added to at least one Organization Catalog. (5)

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

    • When creating a 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. (6)

    • Linux VM Templates (CentOS/Ubuntu/RHEL):

      • Update the values for HCP_FQDN & run the following command on the Linux VM Template.

/bin/yum -y install curl

/usr/bin/apt-get update && /usr/bin/apt-get -y install curl; curl -Ls

https://repo.skygrid.cloud/repo/6.x/6.5.2/LATEST/agents/hcp_linux_agent.sh

bash -s

https://repo.skygrid.cloud/repo/LATEST

AUTO_INSERT <HCP_FQDN>_https://<HCP_FQDN> 5671 docker.skip

  • Windows VM Templates: 

    • Update HCP_FQDN & run the following in CMD Prompt

PowerShell.exe -ExecutionPolicy Bypass -Command

 "Invoke-WebRequest

https://repo.skygrid.cloud/repo/6.x/6.5.2/LATEST/agents/hcp_agent_install_windows.ps1

OutFile hcp_agent_install_windows.ps1 ; & .\hcp_agent_install_windows.ps1 https:// repo.skygrid.cloud/repo/LATEST 

AUTO_INSERT <HCP_FQDN>_https://<HCP_FQDN> 5671 docker.skip"(7)

Note

Caution

  • (1) If the same vCenter Server will be used by more than one HCP, then clone the same VM Template for each HCP.

    • Example: use a Prefix, VMT-HCP-PROD-Win2k16x64, and VMT-HCP-QA-Win2k16x64 which will be used by the PROD and QA HCP respectively.

      • Clone the Guest Customization too and ensure the name matches the VM Template name.

  • (2) Update the HyperCloud_Platform_PROD_FQDN to HyperCloud_Platform_QA_FQDN for customizing VMs deployed from other HyperCloud_Platform(s).

  • (3) For Linux VMs, remove the older version of the kernel and reboot the system.

  • (4) Only vApp Templates created in vCloud or imported from vCenter are supported. ISO and OVA formats are not supported.

  • (5) Use HyperCloud Blueprints to create a multi-tier deployment.

  • (6) Use this only if the VMs deployed using HyperCloud do not have internet access.

  • (7) For Hyper-V & KVM, run the following before shutting down the VM Template:
    sysprep.exe /oobe /generalize /shutdown /mode:vm # /unattend: Use an unattend.xml if available.