Architecture pattern for deploying HCX on VMware Cloud Foundation consolidated architecture
This architecture pattern explains how to deploy VMware HCX™ on VMware Cloud Foundation for VPC consolidated architecture deployment in IBM Cloud VPC. With HCX, you can streamline workload migration, manage workload rebalancing, and ensure business continuity across data centers and clouds.
An overview of this architecture pattern is shown in the following diagram.
To obtain image to install the required software in this architecture pattern, raise an IBM Cloud Support ticket to IBM Cloud® for VMware Solutions.
Deploying HCX on VMware Cloud Foundation consolidated architecture deployment
The following diagram introduces the high-level steps to deploy HCX on a VMware Cloud Foundation consolidated architecture.
This architecture pattern deployment is summarized as follows:
- Create one bare metal server VLAN interface for HCX Manager into the Virtual Private Cloud (VPC) management subnet. Attach the interface to the existing management security group. Add required DNS A and PTR records to the DNS service.
- Deploy the HCX Cloud manager appliance and integrate it with vCenter and NSX manager. Plan and size your HCX deployment.
- Create the required number of bare metal server VLAN interfaces with reserved IP addresses by using consecutive IP range into the management domain's management (minimum 2) and vMotion (minimum 1) subnets for HCX appliances (IX and NEs). Attach each interface to the existing management and vMotion security groups.
- Create HCX network profiles for a combined management and uplink and vMotion in HCX Manager by using the IP addresses created in the previous step.
- Create an HCX compute profile for the HCX fleet components by using the created network profiles in HCX Manager.
Considerations for deploying HCX on VMware Cloud Foundation consolidated architecture
When you design or deploy this architecture pattern, consider the following information:
- Currently, VMware Cloud Foundation for VPC supports to be a source only when you create site peering and service mesh over a public network. Therefore, HCX shows as a source, but migration is still possible both ways. HCX appliances use IBM Cloud VPC public gateway for the egress traffic. For more information, see Architecture pattern for HCX site peering and service mesh in IBM Cloud.
- Private networking supports both source and destination HCX site peering deployments.