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:

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:

• VM Templates:

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