Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2

Overview 


Following are minimum requirements for managing VMware vCloud Director using HyperCloud Portal
General

  • VMware vCloud Director must be accessible to the HyperCloud™ Platform using FQDN.
  • VMware vCloud Director must be configured with VMware NSX
    • Network Pools must be backed by VxLAN.

Note: HCP VM deployment translates to 1 vApp in vCloud Director. Hence creates vApp networks when 1 VM is deployed via HyperCloud™ Platform.

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

Compute & Storage (Organization vDC)

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

Virtual Networking

  • Each organization vDC must have at least 1 Edge Gateway connected to Provider Network
  • Provider Network must be configured and have a set of IP Pool for NATing HCP deployed VMs.

Important Note: HyperCloud™ Platform will assign and configure NAT on Edge Gateway using IPs from provider Network, if configured in HCP IP Pool.

  • Each Organization must have at least 1 Organization Networks preconfigured.
  • vApp Networks will be created by HyperCloud Portal using the Network Pool backed by VxLAN

Important Note: HCP deploys 1 vApp per VM and hence creates vApp networks for each VM.
VM templates

  • VM Templates must be pre-created and added to vCD Public or Organization Catalog
  • VM Template preparation: Refer Appendix-A and Appendix-B for VM Template preparation guidelines

Important Note: Multi-Tier vApp templates are no supported. This feature is available using HCP Blueprints.

  • No labels