Cloud Director Service on Google Cloud VMware Engine Deployment- part 2 CDS Instance Creation

In last section, we have seen how to enable CDS, vRops and Chargeback service from VMware Cloud. As we mentioned that CDS will not create instance we enabling service because we need to login CDS console to choose right region based on where your workload/end customer is.

Starting from https://console.cloud.vmware.com and click VMware Cloud Director will direct CDS instance page,

When creating CDS, the following information will be required

• An environment which the region you want to deploy the instance
• Upgrade category of the upgrade track and station
• Administrator password

We will see the instance is being created and more detail in Activity log show progress.

Since this is only for a demo to create instance, we will cancel the creation and using existing instance that also in Tokyo region.

To use the service, first you must configure and deploy a reverse-proxy client VM that connects with CDS. Then, you can associate CDS to the SDDC through the proxy connection.

Prerequisites of CDS proxy is you need to be network administrator role which will be used to generate VMware Cloud API token, besides prepare FQDN and IP address of GCVE vCenter and NSX.

Under VMware Cloud console, click your name>My Account>API Token and Generate Token. Again make sure Network Administrator is checked.

The download OVA file will be then processed and we may find progress in Activity log, then you may download it into your jump host and import into GCVE vCenter.

Before deploying Proxy VM, in the NSX of GCVE, create a network segment for the reverse proxy appliance to us. eHere I will skip the procedure of deploying OVA in vCenter and go to the Proxy VM console directly, you need to Proxy VM can talk to vCenter, NSX and public internet, to verify to ensure the service is active and running, run systemctl status transporter-client.service and transporter-stauts.sh. Otherwise the connectivity between GCVE vCenter and CDS will not be functional.

After we deploy the reverse proxy appliance in the GCVE and all network connectivities perform well, we can associate infrastructure resources in GCVE and instance of CDS.

In this step, we will need credential of vCenter and NSX.

Upon submitting we may monitor the status and progress and in few minutes we should be able to integration done and click open instance it will ask to give account information.

Now in the CDS we may see that vCenter and NSX have been added automatically.

CDS also helps us to create PVDC that linked to GCVE vCenter Resource Pool.

Likewise, the T0 Gateway or Provide Gateway is setup, by default the block is 100.68.1.0/23.

Wrap up, as we through the deployment we found that CDS is really asset-light for partner to rapidly expand or burst cloud footprint to new geographies to support customer in PSYG model. It brings all support under VMware to reduce operational overhead and deliver partners consistent experience.