What’s Required For vSphere Stretch Deploy To Work With vCloud Hybrid Service | VMware vCloud Blog – VMware Blogs

Posted on August 7, 2013 by 

By: Chris Colotti

This is a repost from Chris Colotti’s blog, chriscolotti.us

I wanted to run through a quick guide to what is needed to work with vCloud Hybrid Service and how things are setup to get it working.  There is a misconception that getting this working is really hard to do, but I hope you will see that is not in fact the case.

Stretch Deploy Appliance Requirements

The following virtual appliances are needed in order to begin the setup of Data Center Extension and Stretch Deploy, which by the way, are the same thing

  • vCloud Hybrid Services Public Cloud Account
  • vSphere vCenter on premise
  • vCloud Networking and Security Manager On Premise
  • vCloud Connector Appliances On Premise
    • vCC Node on Premise
    • vCC Server on Premise
  • vCC Multi-tenant Node at vCloud Hybrid Service (This is already deployed by VMware and you just need the appropriate URLS)
    • Yours will be different but will look something like mine below
    • My Dedicated Cloud vCC Node:  p1v17-vccmt.vchs.vmware.com:443
    • My Virtual Private Cloud vCC Node: p1v14-vccmt.vchs.vmware.com:443

Step 1 – Configure vCloud Networking & Security Manager

This is as easy as getting the OVA file from the download site and importing into vSphere on premise.  Once it is imported you need to simply register it with vCenter Server so it can issue the commands needed.  Once this is deployed you can move onto configuring the vCloud Connector components as the login information and IP of the vCNS Manager are needed.  There are a couple of things you will want to also consider.

  1. Update the admin/default login information
  2. Update the time and NTP settings
  3. DNS information

Step 2 – Configure vCloud Connector

This is probably the step that most people struggle with initially, but once it’s setup you are golden, but there is a few things you need to do specifically for Stretch Deploy to work on the vCloud Connector Nodes.  Below is the basic steps you need to perform to get vCloud Connector setup.

  • Deploy and configure the vCloud connector Node on Premise
    • Configure IP Addressing, Time,
    • Change admin passwords
    • Configure local vSphere Connection
  • Deploy and configure the vCloud Connector Node on Premise
  • Configure IP Addressing, Time
  • Change admin passwords
  • Add License Key
  • Register with vSphere vCenter Server

  • Add vCloud Node Connections
    • Click Register Node
    • Fill in information
    • Select vSphere or vCloud Target
    • Supply credentials

  • Finally enable the nodes for Stretch Deploy
    • Notice the vSphere node is asking for the vShield Manager URL and login
    • vCloud is asking for the Org Login information

At this point vCloud Connector is configured and you still need to perform one last step which is to deploy a vShield Edge Gateway on premise.

Step 3 – Deploy On Premise vShield Edge Gateway

I touched on some of this in the previous posts, but I will repeat some of the things to consider here.  It’s not a requirement that in a vSphere setup that existing virtual machines are changed to use this as their gateway.  We need only deploy this Edge Gateway to serve as a VPN end point to the vSphere port group we want to stretch.  You only need to deploy a new Edge with the following basic settings:

  • vnic0 – External Network (Mapped to a Port Group with Internet Access
  • vnic1 – Internal Network (Mapped to the Port Group you want to extend)
  • Firewall Rules = Default
  • NAT Configuration = Default

In order to add a new vShield Edge Gateway you need to select the Data Center level object in vSphere, click the Network Virtualization tab and add a new Edge with the correct mappings and settings as above.  You will need to give it IP addresses on both Portgroups as well.

When you are done you will have a network that looks something like the logical diagram below where the new Edge Gateway is simply bridging the VLAN portgroup you want to stretch and a port group with internet access.  All the virtual machines will remain untouched.

Step 4 – Configure vCloud Connector Plugin

Once you have all these parts in place you simply need to finish the vCloud Connector Plugin setup in vSphere to add your two clouds so you can begin the stretch deploy process.

Summary

You can see there is really only four major steps to set up the components needed to make vSphere and Data Center Extension (Stretch Deploy) work.  Yes there is a few things you need to deploy and configure, but that’s the same with any feature rich technology.  I hope between this ad my other recent posts with another one still to come you can see that this is pretty simple to get setup.  Give it a try to start moving workloads to vCloud Hybrid Service!

Chris is a Consulting Architect with the VMware vCloud Delivery Services team with over 10 years of experience working with IT hardware and software solutions. He holds a Bachelor of Science Degree in Information Systems from the Daniel Webster College. Prior to VMware he served a Fortune 1000 company in southern NH as a Systems Architect/Administrator, architecting VMware solutions to support new application deployments. At VMware, in the roles of a Consultant and now Consulting Architect, Chris has guided partners as well as customers in establishing a VMware practice and consulted on multiple customer projects ranging from datacenter migrations to long-term residency architecture support. Currently, Chris is working on the newest VMware vCloud solutions and architectures for enterprise-wide private cloud deployments.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s