VMware lately introduced the overall availability of assist for Cloud Director service with Google Cloud VMware Engine as an SDDC endpoint. As a supplier, you may leverage a multi-tenant Google Cloud VMware Engine as an SDDC endpoint for a manufacturing atmosphere or to function a catastrophe restoration location for an on-prem VMware Cloud Director deployment or one other hyperscaler primarily based SDDC endpoint that’s serving as a manufacturing atmosphere.
This weblog is the primary in a sequence to show methods to setup the atmosphere to implement CDs with Google Cloud VMware Engine for multi-tenancy. The image of the reference structure under depicts the goal configuration as proven within the setup documentation.
The next are particulars on the perform of every element coated within the demo and why they’re required:
- Supplier Mission – The supplier challenge is the GCP challenge you because the supplier personal that the Google Cloud VMware Engine will probably be deployed in and that the tenant initiatives will connect with for another companies you might present corresponding to companies backed by Google native companies. Within the diagram under, the supplier challenge is the inexperienced field within the higher left hand nook.
- Supplier Owned Buyer/Tenant Mission – The supplier owned buyer/tenant challenge is the GCP challenge you because the supplier personal and handle for every tenant that will probably be deployed. The challenge serves as a touchdown spot for all ingress and egress site visitors from the tenant’s presence in Google Cloud VMware Engine.
- These initiatives make sure the tenant site visitors is remoted for every tenant traversing a VPN from their NSX-T T1 within Google Cloud VMware Engine to a VPN system contained in the tenant’s challenge.
- This challenge could possibly be the one presence the tenant has in GCP or the tenant might have their very own GCP presence that the challenge is peered to. Within the diagram under, the highest center inexperienced field depicts a tenant with out another GCP presence, so all ingress and egress site visitors leaves this challenge with out traversing another hops in GCP. The center purple field depicts a tenant that additionally has their very own GCP presence (backside center purple field), so all ingress and egress site visitors goes from the supplier owned tenant challenge to the shopper’s GCP challenge by way of a peering connection.
See the next video demo on methods to setup the supplier challenge, tenant networking and making a Google Cloud VMware Engine to affiliate to CDs.
For the complete directions on methods to configure VMware Cloud Director service with Google Cloud VMware Engine, see the our documentation.
Catastrophe Restoration and Migration Help
Catastrophe restoration and migration is supported into Google Cloud VMware Engine by VMware Cloud Director Availability from on-prem deployments of VMware Cloud Director, different hyperscaler endpoints, in addition to different Google Cloud VMware Engine non-public cloud endpoints. For extra info on methods to configure Google Cloud VMware Engine with VMware Cloud Director Availability, see DR and Migrations to VMware Cloud Director service Utilizing VMware Cloud Director Availability .