Purpose : This document lists all the activities required before deploying HDM on Cloud Director/VMware Cloud Director (VCD).
Tasks to be completed before starting On-Premise HDM deployment :
-- For more details, refer the HDM documentation link :
https://docs.primaryio.com/hdm%20doc%202.2/cds/deployment%20planning
| S.No | On Premise tasks | Task purpose and expectation | When will I need this information? |
| 1 | Decide the HDM deployment mode -- standalone or cluster | HDM can be deployed in two ways (standalone or cluster). Factors to decide will be, based on the availability of the resources in the environment | Selection required during On-Premise HDM deployment |
| 2 | Decide the HDM resource allocation type. (Ultra lite, Lite, standard and performance) | Factors to decide will be, based on the availability of the resources in the environment. (CPU, Memory, storage) versus the concurrent migration capacity | Selection required during On-Premise HDM deployment |
| 3 | Decide whether to install HDM with static or DHCP IP allocation | Based on the environment you can make a choice | Selection required during HDM appliance and On-Premise HDM deployment |
| 4 | Decide whether to install HDM with multi or single network environment? | An ideal network configuration isolates various types of network traffic for maximum security, performance, and access control. So HDM assumes five networks in the typical environment. 1. HDM Management Network (VM Network), 2. ESXi Network (ESXi_Network),3. HDM Internal Network (HDM_Internal_Network), 4. WAN Network (Uplink_WAN_Network), 5. Application Network: You need to map your network/s with these five HDM network categories during HDM installation. *More details about these networks | Selection required during HDM Appliance and On-Premise HDM deployment |
| 5 | Reserving and gathering assigned IPs and other network related information for the five HDM Network categories | Refer the link and download the template for calculating IP requirement. https://docs.primaryio.com/Planning%20Template.xlsx Keep the information handy during HDM Appliance and On-Premise deployment. | Unique IP's should be allocated during HDM Appliance and On-Premise HDM deployment. Additionally Gateway, Subnet mask, DNS information is also required during deployment. |
* HDM network categories :
- Management Network (VM Network): This network usually maps to the VM network and provides access to vCenter. All management API communications with vCenter take place over this network.
- ESXi Network (ESXi_Network): This network usually maps to the VM network and provides access to ESXi.
- HDM Internal Network (HDM_Internal_Network): This network is used by HDM for communication among its components. It is recommended to configure a dedicated low latency network for this purpose.
- WAN Network (Uplink_WAN_Network): This network provides access to the cloud. All data transfers between the on-premises and cloud environments take place over this network, via either a public link or a direct connection.
- Application Network: This network facilitates application VM data transfers; each application can employ its own network.
--------------------------------------------------------------------------------------------------------------------
Tasks to be completed before starting On-Cloud HDM deployment :
-- For more details, refer the HDM documentation link :
https://docs.primaryio.com/hdm%20doc%202.2/cds/deployment%20planning
| S.No | On cloud tasks for VCD | Task purpose and expectation | When will I need this information? |
| 1 | Gather cloud information | vCloud Director FQDN, Organization name, user name and password (with admin privileges) | Information required during On Cloud HDM deployment |
| 2 | Create Isolated network and assign IP range to this network (minimum 50) if planning for static HDM deployment | Network used for Internal data transfer between on cloud HDM components and the VM's. IP's assigned to this network will be consumed by the On Cloud HDM components and also by the On Cloud migrated VM's during booting | Network details (IP range, gateway and subnet mask) required during On Cloud HDM deployment |
| 3 | Create Routed network assign IP range (minimum 2) to this network if planning for static HDM deployment | Network used for communication with premise side WAN network | Network details ((IP range, gateway and subnet mask)) required during On Cloud HDM deployment |
| 4 | Create IPSec tunnel | VPN channel for communication between On Premise-WAN network and On Cloud WAN network. Successful result of ping test from On-Premise to the On Cloud gateway (If you have configured advanced firewall rules, ensure that ICMP traffic is allowed.) | NA |
| 5 | Create a new vApp | HDM components will be deployed in this vApp | vApp name during on cloud HDM deployment |
| 6 | Attach the Isolated and Routed networks created above to vApp created above | To deploy HDM components in the vApp and also used during migrating VM's to the vApp | NA |
| 7 | Setting up Firewall rules | Add recommended firewall rules by specifying source and destination subnet with service any. More details about rules is described in the admin guide | NA |