As part of the VCPS delivery and acceptance process, VMware validates a two-site HCX deployment. One is the enterprise site, and the other is the Cloud site.
As a Cloud Provider, you will deliver the SDDC during the VCPS bring-up which acts as the Cloud Site in an HCX deployment pair.
To validate the functionality of HCX on this primary SDDC, VMware requires a 2nd HCX deployment that will act as the enterprise site.
This enterprise site represents a customer's on-prem site in a production deployment. During validation, the VCPS scripts deploy the enterprise HCX appliance, configure HCX, create the site pair back to the Cloud site and test the service mesh. The VCPS scripts deploy the enterprise HCX appliance but do not deploy the enterprise SDDC.
The enterprise SDDC must meet the following requirements, and you must create and maintain the SDDC.
|vCenter Server||The vCenter Server that will be deployed must be at a version compatible with HCX as per the interop matrix. See the interoperability matrix for detailed information.|
|SDDC||For the vCenter Server deployment, the following constructs must be created. These constructs are referenced in the SDDC Enterprise bring-up script.
Note: The names for the data center, cluster, and so on are only examples and can be adjusted as per the specification file.
|HCX Enterprise Input Specification File||The HCX specification file must contain the details similar to the SDDC input specification file, and in addition must have the required HCX information, such as the entrprise credentials, site pair specification, Service Mesh information, and so on.|
See the Appendix for example specification files.