Versions Compared

Key

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

...

  • General:

    • VMware vCenter Server is mandatory. [1]

  • Compute & Storage:

    • HyperCloud uses the concept of an Availability Zone which maps to:

      • One or more vSphere datacenters.

      • One or more vSphere clusters with one or more shared storages (VSAN, iSCSI, NFS, or FCP).

  • Virtual Networking:

    • One or more distributed switches managing the vSphere Cluster Networking.

    • One or more routable (DHCP) VLANs backed distributed port groups for VMs preconfigured in vCenter Server.

    • Distributed Switch physical uplinks must be configured to trunk all VM VLANs.

  • Authentication:

    • Use a service account (example: hc_vcenter_svc@vsphere.local) for connecting the HyperCloud to vCenter Server with the following permissions:

      Code Block
      languagebash
      Datastore > Browse 
      Datastore > Allocate Space 
      Virtual Machine > Configuration > <Select All Permissions>
      Virtual Machine > Inventory > <Select All Permissions> 
      Interaction > <Select All Permissions> 
      Provisioning > Customize 
      Provisioning > Deploy Template 
      Provisioning > Read Customization specifications 
      Network > Assign Network 
      Resource > Assign Virtual Machine to Resource Pool

...

  • General:

    • Hyper-V Nodes must be set up in a Fail Over Cluster. [1]

  • Compute & Storage:

    • HyperCloud manages Hyper-V nodes using a Host agent (proxy).

    • This agent must be installed on all Hyper-V Server.

    • Update the value of < HCP_Proxy_Password > using the following command with Run As Administrator privileges:

      Code Block
      languagepowershell
      PowerShell.exe -ExecutionPolicy Bypass 
      -Command "get https://repo.skygrid.cloud/repo/6.x/6.5.2/LATEST/proxy/HyperVProxy_Install_Windows_v1.3.ps1 
      OutFile ProxyInstaller.ps1; & .\ProxyInstaller.ps1 4434 <HCP_Proxy_Password>"
    • Hyper-V Node must be configured with Clustered Storage Volumes.

      • One Cluster Shared Volume (CSV) for VM Templates (vhdx) Storage.

      • One Cluster Shared Volume (CSV) for deploying VMs using HyperCloud Portal.

    • HyperCloud uses the concept of an Availability Zone which maps to,

      • One Hyper-V Failover Cluster Manager

      • One Cluster Shared Volume for VM Template Storage.
        Example: C:\CSVs\Hypercloud_Templates

      • One Cluster Shared Volume for deploying VMs.
        Example: C:\CSVs\Hypercloud_Production.

  • Virtual Networking:

    • Hyper-V vmSwitch and its NIC must be configured to trunk all or required VLANs.

    • DHCP IP Addressing must be configured for the VLAN selected during VM Provisioning.

    • VM VLANs must be routable and be able to reach the HyperCloud portal on port 5671. [2]

  • Authentication:

    • Create a dedicated Windows AD service account (
      Example:svc_hcp@domain.com) with the following permissions:

      • must belong to the Active Directory Domain.

      • must not be a member of Domain Admins Group.

      • must be a member of local administrators on each Hyper-V Server.

      • must be allowed Logon as a service right on each Hyper-V Server.

  • VM Templates:

    • VM Templates must be provided as VHDX files and placed in the Share CSV. This path will be configured in the Availability Zone. [3]

Info

Information

...

  • General:

    • Ovirt Manager is mandatory.

  • Compute & Storage: HyperCloud uses the concept of an Availability Zone which maps to:

    • One data center (local or Shared).

    • One storage domain (data) for VMs.

    • One storage domain for VM Templates (local or Shared).

  • Virtual Networking:

    • At least one VLAN backed network pre-created in Ovirt Manager.

    • VM Networks backed by VLANs must have the DHCP IP Addressing enabled.

    • Ovirt virtual switch physical uplinks must be configured to trunk all VM VLANs.

  • VM Templates:

    • VM Templates must be pre-created in the same datacenter as the cluster. [1]

Info

Information:
[1] Refer VM Template Preparation guidelines.

...

  • General:

    • VMware vCloud Director must be accessible to HCP using FQDN.

    • VMware vCloud Director must be configured with VMware NSX.

      • Network Pools must be backed by VxLAN. [1]

    • For connecting HCP to vCloud Director Organization only, ensure that Org Admin User is configured with the Organization Administrator role.

  • Compute & Storage (Organization vDC):

    • Minimum one organization with one organization VDC.

    • Organization vDC must use Storage Policy. Network Pool must be backed by VxLAN i.e. greater than 1000 if deploying a large number of VMs.

  • Virtual Networking:

    • Each Organization vDC must have at least one Edge Gateway connected to the provider network.

    • Provider The provider network must be configured and have a set of IP Pool for NATing HCP deployed VMs. [2]

    • Each Organization must have at least one Organization Networks preconfigured.

    • vApp Networks will be created by HCP using the Network Pool backed by VxLAN. [3]

  • VM templates

    • VM Templates must be pre-created and added to vCD Public or Organization Catalog. [4]

Info

Information:

  • [1] HCP VM deployment translates to one vApp in vCloud Director. It, therefore, creates vApp networks when one VM is deployed via HCP.

  • [2] HCP will assign and configure NAT on Edge Gateway using IPs from provider Network , if configured in HCP IP Pool.

  • [3] HCP deploys one vApp per VM and hence creates vApp networks for each VM.

  • [4] Multi-Tier vApp templates are not supported. This feature is available using HCP Blueprints.

  • Refer to VM Template Preparation guidelines.

...

A firewall is a network security device that monitors incoming and outgoing network traffic , and permits or blocks data packets based on a set of security rules. Its purpose is to establish a barrier between your internal network and the incoming traffic from external sources such as the internet in order to block malicious traffic like viruses and hackers.

...

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

        Code Block

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)

...