Deployment Planning

Deployment Requirements

HDM provides a flexible deployment model to support a wide range of user needs with respect to use cases, performance, scalability, and security. This section will help you choose the correct deployment type and network topology to support your needs.

HDM Deployment Types

While deploying HDM users need to select a combination of Deployment Mode and Resource Allocation type. The features of the available options are provided below to guide the user to choose the deployment type that is best suited for their requirements.

Deployment Mode : Standalone or Cluster

You can choose either a standalone or cluster deployment mode, based on your scale and fault tolerance requirements. Here are a few points to keep in mind:

1. In standalone mode, a fixed number of HDM components are installed, regardless of the size of the on-premises cluster. Also, there is no HDM component redundancy in this mode, so fault tolerance is low.
2. In cluster mode, some HDM components are installed in proportion to the scale of the on-premises cluster to deliver higher redundancy and better fault tolerance. This requires higher resource consumption, but allows a higher number of concurrent migrations, than the standalone option.

Resource Allocation : Ultra-Lite, Lite, Standard, or Performance

HDM provides ultra-lite, lite, standard, and performance deployment options. The trade-off between them is CPU and memory resource utilization, versus the concurrent migration capacity. Here are a few points to keep in mind when choosing the option that best fits your needs:

1. Ultra-lite is the least resource intensive of the options. However, it only supports cold migration, and only to VMware Cloud Director.
2. The lite option requires the least number of resources to support all HDM migration use cases. However, it is limited in the number of parallel migrations and number of concurrently migrated VMs, compared to standard and performance deployment options.
3. The standard option is more scalable but requires more resources than the lite option, but is less scalable and requires fewer resources than the performance option.
4. The performance option requires the highest number of resources, but it provides the highest number of parallel migrations and number of concurrently migrated VMs.

More details on the resource requirements for these deployment options is available in the next section.

NOTE: Ultra-lite is the only mode that supports migration to VMware Cloud Director.

Concurrency and Scale Support

HDM queues all migrations requests and is capable of processing eight VMDKs per HDM cluster node.

HDM Resource Requirements

Table 1 lists the resource requirements for each ultra-lite deployment type.

Table 1: Resource Requirements

NOTES:

1. The names ESXMgr and CloudCache are abbreviated names for the VMs containing HDM components. These are created as part of the HDM deployment.
2. The N in Cluster (N) refers to the number of nodes in the cloud cluster.

Prepare Cloud for Deployment

To deploy the HDM solution on IBM Cloud for VMware Solutions Shared you would need to

• Get the Organization Administrator access credentials to the VMware Cloud Director tenant portal.
• Identify the organization ID and save for later use.
• Create a new user with administrator privilege.

Identify the organization ID

• Login to the tenant portal
• The Organization ID can be identified from the location in Figure 1

Figure 1: Screenshot show how to identify Organization ID

Create new user with Organization Administrator privilege

We recommend the creation of a new organization administrator for HDM integration. We refer to this administrator in the rest of the documentation.

1. Create the new Org administrator user using procedure here to create new user.
2. Make sure you give it the Organization Administrator role see Figure 2.

Figure 2: Setting role for created user to Organziation Administrator

Figure 3: Set the quota to unlimited

From the steps above please capture the information in the table below. The username is the newly created user with administrator privileges. You will need this part of the cloud deployment.