Service Orchestration Requirements

Overview

Service Orchestration is the coordination and arrangement of multiple services exposed as a single aggregate service. Developers utilize Service Orchestration to,

• Support the automation of business processes by loosely coupling services across different applications and enterprises.

  • Creating second-generation, composite applications.

• In other words, service orchestration is the combination of service interactions to:

  • Create higher-level business services.

This topic describes the requirements for HyperCloud™ Platform (HCP) to manage & provision Virtual Machine(VMs) to multiple cloud providers:

Prerequisites

Firewall Requirements

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.

All applicable firewalls must be configured with the following ports:

VM Template Preparation

VM Template Preparation (non-cloud-init)

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.⁽¹⁾

• 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: ^[2]

• VM Tools:

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

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. ⁽³⁾

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. ⁽⁴⁾

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

• 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. ⁽⁶⁾

  • 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

VM Template Preparation (cloud-init)

VMware vSphere Requirements:

• VM Tools:

  • VMware Tools must be installed on the VM Template or customization will fail.

  • Refer VM Template Preparation (Installing Cloud-Init)

Microsoft Hyper-V Requirements:

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

• Refer VM Template Preparation (Installing Cloud-init) below,

  • Open Virtualization (Ovirt) KVM Requirements

    • Ovirt Guest Agent & tools must be installed as described in Ovirt Guest Agent & tools. ⁽¹⁾

VMware vCloud Director: Not Supported

VM Template Preparation (Installing Cloud-init):

• Linux VM Templates (CentOS/Ubuntu): Update the following values:

  #CentOS
  #----------
  sudo yum update -y
  sudo yum install -y cloud-init

  # Update /etc./cloud/cloud.cfg
  # to allow root and password authentication run the following command
  sudo sed -i 's/ssh_pwauth: false/ssh_pwauth: true/g' /etc./cloud/cloud.cfg
  sudo sed -i 's/disable_root: true/disable_root: false/g' /etc./cloud/cloud.cfg

  #vim:syntax=yaml
  datasource_list: ["NoCloud", "ConfigDrive"]

  
  CentOS 6.x and below*

  #---------------------------

  #remove udev rules for network adapters
  rm /etc./udev/rules.d/70-persistent-net.rules

  
  #Ubuntu

  sudo apt-get update
  sudo apt-get upgrade -y
  sudo apt-get install cloud-init -y

  #Edit 90_dpkg.cfg to remove items in datasource_list except the following
  datasource_list: [ NoCloud, ConfigDrive, None ]

• Windows VM Templates (Window 2016):

  • Windows VM requires cloudbase-init for Guest Customization. Run the following command to install Cloudbase-init. ⁽³⁾

Update the following 3 files as shown below before running sysprep via CloudBase-Init Installer

Once all 3 files are edited, return to the Cloudbase-Init installer and select Sysprep and click Finish. This will generalize the system and shut down the VM. Mark the VM as a template based on the Hypervisor of your choice.

Cloud Provider Requirements

VMware vSphere Provider Requirements

VMware vSphere was formerly known as VMware Infrastructure. This is the brand name for VMware's suite of server virtualization products that:

• Includes its ESXi hypervisor and vCenter management software.

• Undergoes periodic revisions and updates to add features; modifications to the application program interface (API), and changes to the ESXi shell.

The following are the minimum requirements for managing VMware vSphere using HCP:

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

    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

• VM Templates:

  • VM Templates must be pre-created and marked as templates in the VMware vCenter Server. ^[2]

Microsoft Hyper-V Provider Requirements

Microsoft Hyper-V is virtualization software that, well, virtualizes the software. It can not only virtualize the operating systems but also the entire hardware components, such as hard drives and network switches. Unlike Fusion and Virtualbox, Hyper-V is not limited to the user’s device; you can use it for server virtualization as well.

The following are minimum requirements for managing Microsoft Hyper-V using HCP:

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

    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]

Open Virtualization Manager (Ovirt) KVM Provider Requirements

Following are the minimum requirements for managing Ovirt KVM using HyperCloud:

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

VMware vCloud Director Provider

Following are minimum requirements for managing VMware vCloud Director using HCP:

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

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