Certified Reference Design for Service Providers

Certified Reference Design for Service Providers 2.0

The Certified Reference Design (CRD) for VMware Cloud Providers is a pre-validated set of software components that simplify the deployment of a VMware vCloud Director based multi-tenant Cloud in a predictable and efficient manner.
Even if not yet completely automated, the intent of the CRD is to reduce the complexity of deploying, upgrading, and managing dependencies between the VMware components required for a vCloud Director based service.

Check it out here: https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/vcat/vmware-certified-reference-design-core-2-0.pdf

CRD 2.0
CRD 2.0

vCloud Director Extender configuration – Tenant side

In this second post about vCloud Director Extender, I’ll guide you through the necessary steps to configure the vCloud Director Extender Service from a Customer (Tenant) perspective.

vCloud Director Extender enables a Tenant to cold or warm migrate its workloads from vSphere to a vCloud Director based Public Cloud. All the easy steps are wizard-driven and the Tenant also has the option to leverage the automatic creation of a L2VPN connection that can stretch the networking between on premises and the vCloud Director Cloud.

You can read vCloud Director Extender release notes here.

vCloud Director Extender Tenant deployment

All the initial steps needed on the Tenant side are the same we’ve seen on the Service Provider side, first you download the vCloud Director Extender OVA file, then you deploy it in your source vCenter. See the Service Provider Setup paragraph in my previous post to view all the steps.
The only difference you must pay attention to is to choose “cx-connector” as the deployment type.
vCloud Director Extender - Architecture

vCloud Director Extender Tenant configuration

Once deployed, you can access the vCloud Director Extender Virtual Appliance via https on the configured IP Address.
You will be presented with the OnPrem Setup page.
Enter your Local or vCenter (SSO) credentials to access the application and start the configuration wizard.
vCloud Director Extender - Tenant Setup

Select “SETUP WIZARD” to start the Service configuration.
vCloud Director Extender - Tenant Setup Wizard

In Step 1, you’ll enter the parameters needed to connect to the source vCenter. Then click “Next”.
vCloud Director Extender - OnPrem vCenter

Wait for the confirmation message, then click “next”
vCloud Director Extender - OnPrem vCenter OK

In Step 2, you confirm the registration of the vCloud Director Extender as a plugin in the source vCenter, then click “Next”.
vCloud Director Extender - Register Plugin

Wait for the confirmation message, then click “Next”.
vCloud Director Extender - Plugin OK

In Step 3, provide the parameters needed to configure the Tenant Replicator service, then click “Next”.
vCloud Director Extender - Tenant Replicator

Wait for the confirmation message, then click “Next”.
vCloud Director Extender - Replicator OK

In Step 4, you provide the parameters needed to activate the Replicator, then click “Next”.
vCloud Director Extender - Activate Replicator

Wait for the confirmation message, then click “Next”.
vCloud Director Extender - Activate Replicator OK

In Step 5, we’ve finished the OnPrem Setup. Click “Finish”.
vCloud Director Extender - Finish

After the initial Wizard that provides the connection to the source vCenter and the Replicator Service setup, you must access the “DC Extensions” tab to provide necessary parameters to deploy the L2VPN Appliance.
If NSX Manager is deployed on Premises, it is mandatory to choose “ADD NSX CONFIGURATION”.
In our scenario, we don’t have NSX on Premises so we’ll choose “ADD APPLIANCE CONFIGURATION” in the L2 Appliance Configuration section.
vCloud Director Extender - L2VPN Appliance Deploy

Provide the needed parameters to deploy the L2VPN Appliance. Pay attention to the following fields: Uplink Network, which maps to the PortGroup that grants Internet connectivity to the appliance, and Uplink Network Pool IP, which is the source IP Address used to connect to the L2VPN Server. Click “Create”.
vCloud Director Extender - L2VPN Appliance Creation

Wait for the confirmation message that confirms the L2 Appliance configuration.
vCloud Director Extender - L2VPN Appliance Setup OK

This concludes the configuration steps for the L2VPN appliance.
Accessing the Web Client, the Tenant can now configure L2 Extensions and manage workloads migration to the Cloud.

 

vCloud Director Extender Tenant operations

After the configuration steps ends, you can find a new Service registered in the source vCenter inventory: vCloud Director Extender. Click on the icon to launch the Management page for the Service.
vCloud Director Extender - Web Client Plugin

On the vCloud Director Extender management page, you can find two dashboard that show you the overall Migration Health and the DC Extension Status for the L2VPNs.
Select “New Provider Cloud” to connect to your Service Provider.
vCloud Director Extender - Web Client UI

Provide a descriptive name for the target Cloud, the URL of the target vCloud Director Organization for the Tenant, the URL of the target Extender Cloud Service (provided by the Service Provider) and finally your Org Admin credentials. Click “Test” to test the connection, wait for the confirmation message  then click “Add”vCloud Director Extender - Add Provider

You can now see your target vCloud Director Organization appearing in the Provider Clouds tab.
vCloud Director Extender - Provider Running

We’ll now create a new L2 Extension from onPrem to the Cloud. Access the DC Extensions tab and click on “New Extension”.
vCloud Director Extender - New Extension

Enter a name for this extension, select the source Datacenter, the source Network, the target Provider Cloud, vDC and Org Network. The “Enable egress” option enables you to have a local default gateway in each site with the same IP address, to optimize Egress traffic. With Egress optimization enabled, packets sent towards the Egress optimization IP will be routed locally by the Edge, everything else will be sent thru the bridge.
Click “Start” to enable the connection and make the L2 extension.
vCloud Director Extender - New Extension Start

In the vSphere Web Client task console, you can view the “Trunk” Port Group being created with a SINK port. You can also see the Standalone Edge deployment is in progress.
vCloud Director Extender - Task Console

After the tasks complete, you can see the L2VPN status as “Connected”. L2 Extension beetween the source and the target network is in place, so you can safely migrate your workloads to the Cloud without change in IP addressing, keeping the same connectivity you have on Premises. This is really Hybrid Cloud!
vCloud Director Extender - L2VPN Connected

In the vCloud Director Extender Home, you can now see the DC Extension Status dashboard showing the L2VPN Tunnel is in place.
vCloud Director Extender - L2VPNClient Connected Dashboard

If we look at the L2VPN Statistics in vCloud Director, we can see the Tunnel Status as “up”.
vCloud Director Extender - L2VPN Connected vCD

It’s now time to migrate a workload to the Cloud leveraging this new L2VPN Tunnel to keep connectivity with on Premises. Access the Migrations tab and click on “NEW MIGRATION”.
vCloud Director Extender - New Migration

Select the type of migration you want to perform: Cold migration requires the source VM to be powered off while Warm migration enables you to keep your VM runnning on Premises, starting a continuous file sync to the Cloud and completing the cutover when replica is completed. As the wizard highlight, Warm migration is not a vMotion. Click “Next” after the selection.
vCloud Director Extender - Cold Warm

Select the source VM(s), then click “Next”. You can select more than one VM for each migration job.
vCloud Director Extender - Select VM

Specify the target Cloud parameters: target Cloud, vDC, Storage Profile, Org. Network and vApp layout to create if you are migrating more than one VM. Click “Next” when finished.
vCloud Director Extender - Target Parameters

Specify when you want to start the synchronization, the target RPO and the disk type (thin, thick). You can additionally specify a Tag for this migration job. When finished, click “Start”.
vCloud Director Extender - Migration Finish

When the synchronization finishes, the workload will have a Status named “Cutover Ready”. This means that you can start the cutover process, that will Power Off the source VM and will Power On the VM in the Cloud. Click “Start Cutover” to specify the cutover parameters and start the process .
vCloud Director Extender - Cutover Ready

Specify the target cloud, the desired final power status of the target VM after cutover, then click “Start”.
vCloud Director Extender - Cutover Start

The workload Status will became “Completed” once the Cutover finishes.
vCloud Director Extender - Cutover Completed

The migrated VM will be powered off on Premises.
vCloud Director Extender - VM off onPremises

On the target vCloud Director, we’ll find the migrated VM powered on.
vCloud Director Extender - VM in Cloud

Let’s use PING to test connectivity between VM1, still on Premises, and VM2, migrated to the Cloud. The connection will leverage the L2 Extension between on Premises and the Cloud. (Note: DUP! packets message occurs because I’m working in a nested environment).
vCloud Director Extender - Ping Succeed

There’s a 1:1 mapping between source VLAN and target VXLAN when you configure Datacenter Extension in vCloud Director Extender.
To stretch multiple VLANs you must create different Extensions in vCD Extender.

To show this let’s create a new PortGroup on Premises and a new Org vDC Network in the Cloud to see what happens when we need to create an additional network extension.

We configure a new Extension, mapping a local VLAN to the target Org vDC Network. The Status will show as “Connected” when the creation process finishes.
vCloud Director Extender - New L2 Stretch

Looking at the changes automatically made in vCloud Director, we’ll find the new Org Network added as a stretched interface to the existing Site Configuration.
vCloud Director Extender - ESG New L2VPN Config

This concludes the CX Service On Prem configuration.

vCloud Director Extender configuration – Service Provider side

Soon after the release of vCloud Director 9.0, VMware has released the replacement for vCloud Connector, a new tool named vCloud Director Extender.

vCloud Director Extender enables a Tenant to cold or warm migrate its workloads from vSphere to a vCloud Director based Public Cloud. All the easy steps are wizard-driven and the Tenant has also the option to leverage the automatic creation of a L2VPN connection that can stretch the networking between on premises and the vCloud Director Cloud.

vCloud Director Extender works with vCloud Director 8.20.x and vCloud Director 9.0

You can read the Release Notes for version 1.0 here.

In this first post about vCloud Director Extender, I’ll guide you through the necessary steps to configure the vCloud Director Extender Service from a Service Provider perspective.

vCloud Director Extender Architecture

Before to start, I want to show you the architecture of the Service:

vCloud Director Extender - Architecture

On the Provider Side, we have the following components:

  • vCloud Director Extender: the Virtual Appliance that you download and deploy, known as “CX Cloud Service”. After its deployment and configuration, it is used to provide setup and configuration of the overall CX Service.
  • Cloud Continuity Manager (aka “Replication Manager”): this Virtual Appliance is deployed by the CX Cloud Service and its role is to oversee the work done by the Replicator.
  • Cloud Continuity Engine (aka “Replicator”): this Virtual Appliance is deployed by the CX Cloud Service and its role is to manage the VMs replication between the Tenant’s vSphere environment and the Service Provider’s vCloud Director. The Replicator leverages the new H4 Replication Engine.

On the Tenant side, we only need vCloud Director Extender and the Cloud Continuity Engine.

Let’s start now with the installation and configuration steps on the Service Provider side.

vCloud Director Extender Service Provider Setup

The first step is to access myVMware Website and to download the vCloud Director Extender OVA file, located under the “Drivers & Tools” section of the VMware vCloud Director 9.0 download page.vCloud Director Extender - myVMware

myVMware

Following the “Go to Downloads” link you’ll find the vCloud Director Extender 1.0.0 download page.

vCloud Director Extender - Download

The next step is to deploy the OVA file we just downloaded. Select the target vCenter (tipically the Management Cluster vCenter) and select “Deploy OVF Template”.

vCloud Director Extender - Deploy OVF part 1

Choose “Browse” to select a local file.
vCloud Director Extender - Deploy OVF part 2

Choose the OVA file you download previously from the myVMware Website and select “Open”. Once you’re back on the Select Template page, click “Next”.
vCloud Director Extender - Deploy OVF part 3

Choose a name for the vCloud Director Extender Virtual Appliance as you want it to appear in your vCenter inventory, then click “Next”.
vCloud Director Extender - Deploy OVF part 4

Select a Target Cluster/Host and click “Next”.
vCloud Director Extender - Deploy OVF part 5

Click “Next” on the Review details page.
vCloud Director Extender - Deploy OVF part 6

Click “Accept” on the EULA page after reading it, then click “Next”.vCloud Director Extender - Deploy OVF part 7

Select a virtual disk format, a VM storage policy and a target datastore for the Virtual Appliance, then click “Next”.vCloud Director Extender - Deploy OVF part 8

Select a destination Network (PortGroup) for the Virtual Appliance, then click “Next”.vCloud Director Extender - Deploy OVF part 9

In the “Customize Template” tab, you’ll set all the Virtual Appliance Parameters.
In the Service Provider environment, based on vCloud Director, you must choose the deployment type “cx-cloud-service“.
vCloud Director Extender - Deploy OVF part 10

Click “Finish” after having reviewed your configuration, to deploy the Virtual Appliance.
vCloud Director Extender - Deploy OVF part 11

vCloud Director Extender Service Provider Setup

Once deployed, you can access the vCloud Director Extender Virtual Appliance via https on the configured IP Address.
You will be presented with the Cloud Service Setup page.
Enter your Local or vCenter (SSO) credentials to access the application and start the configuration wizard.
vCloud Director Extender - Configuration Wizard

Select “SETUP WIZARD” to start the Service configuration.
vCloud Director Extender - Setup part 1

In Step 1, you’ll enter the parameters needed to connect to the Management vCenter. Then click “Next”.vCloud Director Extender - Setup part 2

In Step 2, provide the parameters needed to connect to your vCloud Director instance, then click “Next”.vCloud Director Extender - Setup part 3

In Step 3, provide the parameters needed to connect to your Resource vCenter(s), then click “Next”.
vCloud Director Extender - Setup part 4

Wait for the “Successfully linked Resource vCenter” confirmation message, then click “Next”.
vCloud Director Extender - Setup part 5

In Step 4, specify the parameters needed to create the Replication Manager Virtual Appliance, then click “Next”.
vCloud Director Extender - Setup part 6

You will see a progress bar indicating the Replication Manager creation status.
vCloud Director Extender - Replication Manager creation

In Step 5, set the Root password for the Replication Manager Appliance, specify the Public Endpoint URL needed to reach the Service (optional, only needed if the Appliance is behind a Proxy/NAT), then click “Next”.
vCloud Director Extender - Setup part 7

Wait for the activation confirmation message, then click “Next”.
vCloud Director Extender - Setup part 8

In Step 6, specify the parameters needed to create the Replicator Virtual Appliance, then click “Next”.
vCloud Director Extender - Setup part 9

You will see a progress bar indicating the Replicator creation status.
vCloud Director Extender - Replicator creation

In Step 7, set the Root password for the Replicator Appliance, specify Lookup Service URL and credentials for the Resource vCenter and the Public Endpoint URL needed to reach the Service (optional, only needed if the Appliance is behind a Proxy/NAT), then click “Next”.
vCloud Director Extender - Setup part 10

Step 8 will conclude the Wizard. Click “Finish”.
vCloud Director Extender - Setup part 11

vCloud Director Extender – Service Provider L2VPN Server Setup

The last step to enable the Service, only necessary if L2 stretching is needed between the on premises environment and vCloud Director, is to configure the L2VPN Service on the target Organization Virtual Datacenter(s) Edge Gateway(s).
To create L2VPN connections, you need to convert the Edge Services Gateway(s) to Advanced and grant the needed rights to the vCloud Organization.
You can read one of my previous posts, Self Service NSX Services in vCloud Director, to understand how this works and how to complete this part of the configuration, if needed.

At this stage you can configure the L2VPN Server on the Tenant Edge Gateway (this can be done by the Service Provider or can be delegated to the Customer).
L2VPN Server

When you configure an L2VPN Server, you must configure a Peer Site. You’ll configure a dummy Peer Site at this stage, just to conclude the Setup on the Tenant side. We’ll could leave this Peer site disabled because we won’t use it, it will be vCloud Director Extender on the Tenant side to configure the needed Peer Sites on this Edge Gateway.
L2VPN Server - Dummy Peer Site

This concludes the Service Provider side of the vCloud Director Extender Service configuration.
In the next post I’ll show you how to configure the CX Service on the Tenant side.