VMware Cloud Director service with Google Cloud VMware Engine – Half 1

VMware lately introduced the final 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 collection to demonstrator 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 is particulars on the perform of every part lined within the demo and why they’re required:

• Supplier Undertaking – The supplier challenge is the GCP challenge you because the supplier personal that the Google Cloud VMware Engine shall be deployed in and that the tenant tasks will connect with for every other companies it’s possible you’ll 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 Undertaking – The supplier owned buyer/tenant challenge is the GCP challenge you because the supplier personal and handle for every tenant that shall be deployed. The challenge serves as a touchdown spot for all ingress and egress visitors from the tenant’s presence in Google Cloud VMware Engine.
  • These tasks make sure the tenant visitors is remoted by visitors for every tenant traversing a VPN from their NSX-T T1 inside Google Cloud VMware Engine to a VPN machine contained in the tenant’s challenge.
  • This challenge could possibly be the one presence the tenant has in GCP or the tenant may 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 every other GCP presence, so all ingress and egress visitors leaves this challenge with out traversing every other 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 visitors goes from the supplier owned tenant challenge to the shopper’s GCP challenge through a peering connection.

See the next video demo on setup the supplier challenge, tenant networking and making a Google Cloud VMware Engine to affiliate to CDs.