Page Comparison

...

Info

Information

^[1]SaaS-based HyperCloud deployment requires access to VMware vCenter via Public NAT.
- Refer to Firewall for further assistance.
^[2]Refer to Appendix-A and Appendix-B for the VM Preparation guidelines.

...

Info

Information

^[1] HCP does not support Microsoft System Center Virtual Machine Manager.
^[2]See Firewall Requirements.
^[3]Refer Appendix-A and Appendix-B for VM Template preparation Preparation guidelines.

...

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 Appendix-A and Appendix-B for VM Template preparation Preparation guidelines.

...

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 Appendix-A and Appendix-B for VM Template preparation Preparation guidelines.

...

Versions Compared