Home > Blogs > VMware vCloud Blog > Tag Archives: vCloud Connector

Tag Archives: vCloud Connector

Journey To A Full Scale Hybrid Architecture with vCloud Air – Part 3

By: Chris Colotti

In the first post I talked about the basic architecture of a large scale hybrid cloud build out, as well as integrating an on premises view environment into the VMware vCloud® Air™ hybrid cloud.  We extended that Horizon View environment into vCloud Air by adding security servers and global load balancing on the top layer.  You may be asking yourself “why” did we do that?  Well, the ultimate goal of building this out was to mesh together vCloud Air Disaster Recovery and desktops to access those applications.  With the next stage we set out to replicate an internal only application to vCloud Air Disaster Recovery and use DaaS on vCloud Air to give the users access to it once it was failed over.

The Use Case Background

Before we go into the architecture solution we need to understand the problem we are trying to solve.  Many times in the past I have shown how you can fail over public facing applications.  However, not every application is web-based, public facing, or of a “Next Generation” architecture.  In a lot of cases many applications are still internal only and although may be web based, need a desktop on the corporate side to access it.  This is also the case for legacy fat client applications.  So the goal in this architecture was to show how a user can connect to an application on premises and also connect to that same application once vCloud Air Disaster Recovery is invoked to fail it over.  The solution will comprise a few components for illustration, refer to the original overview diagram to understand all the connection points.


  • On premises Horizon View Desktops previously configured
  • On premises “Wiki” based application with a local DNS Entry
  • On premises AD/DNS Servers
  • vCloud Air Disaster Recovery running on the Wiki server ONLY
  • VMware Horizon DaaS on vCloud Air
  • IaaS based AD/DNS with VPN connection to the Disaster Recovery Cloud
  • Cloud to Cloud VPN from Horizon DaaS Cloud to vCloud Air Disaster Recovery Cloud
  • Access to External DNS system
  • A Horizon View Desktop Client

For the purposes of continuing we will assume that the VPN’s and networks are already configured and replication is running on the Wiki Server.  We will also assume from the previous article that the desktop image used for Horizon View on premises is available and ready to synchronize with the new Horizon DaaS cloud.  In order to make this all work we need to first ensure the same desktop image is available in DaaS on vCloud Air for the customer.  We will double click into a few of the virtual data centers above later on.

Synchronizing View and DaaS Images with vCloud Connector

For ease of deployment we created our Horizon View on premises desktop image in vCenter.  We set it up the way we wanted and then used vCloud Connector Content Sync to push a copy of that up to our DaaS on vCloud Air.  This way we are able to subscribe the DaaS catalog to the vCenter version of the image.  vCloud Connector catalog sync then ensures that the DaaS cloud has the same copy available to use.  This is not required and there is other DaaS related things you need to do to utilize the image, but we won’t go into that.  The concept is just to build one image and sync to the cloud(s).  If you want to learn more about Content Sync with vCloud Connector you can watch this video.  Honestly, it’s easy to setup and takes care of ensuring the image is always in sync.  Once you have the image in cloud you can use the admin tools of Horizon DaaS on vCloud Air to create and deploy a desktop pool with the exact same image.

The Fail Over Process (Run Book)

In normal running conditions, the user would connect to view.companyname.com with their Horizon View Client, access their corporate desktop and get to the Wiki Application using http://Wiki01/ from a desktop browser.  In order to ensure the client can get to the same application  during failure we need to invoke a process such as this:

  1. Failover the Wiki Application to the vCloud Air Disaster Recovery cloud
  2. Re-IP the application in the new cloud and power on
  3. Update the local DNS Servers in the IaaS cloud for the Wiki Entry
  4. Re-Direct External DNS for view.companyname.com to point to the DaaS Cloud instead on on Premises View
  5. Clients can then log in and access the same application, 100% cloud based on desktop and IaaS.

For illustration purposes the logical diagrams below show the on premises environment along with the disaster recovery, and IaaS environments.  Remember that the assumption here is all these have the proper cloud to cloud VPN’s and firewall rules setup for network connectivity per the first image.

Below is the On Premises logical architecture.  Notice the desktops are are available behind Horizon View and can connect to “WIKI01”


Below is the Dedicated Las Vegas IaaS cloud that is where the AD/DNS is running for access to directory and name services once fail over occurs.  Recall that VPN connections here are in place between the DaaS cloud and the vCloud Air Disaster Recovery cloud for access to these services.


Below is the Dedicated Las Vegas DaaS tenant logical architecture.  You can see the dtRAM gateways in place on the internet passing connection to the DaaS based desktops in vCloud Air.  Remember this cloud is connected via VPN to the vCloud Air Disaster Recovery cloud so it can access the application below upon fail over.


In the Texas Disaster Recovery Cloud shown below, we can do a full fail over or a test fail over.  In each case the WIKI01 server will be connected to one of the two networks.  Once it is given a new IP address and DNS is updated the DaaS desktops will be able to connect.


Using External DNS To Manage Connectivity

In order to quickly re-direct a user’s View Client from on premises Horizon View to the DaaS desktop and making it transparent to them you need to get creative.  In my case I created the following External DNS records to support this use case.

view.dyn.companyname.org = Public IP of View Secure Gateway (A-Record)
daas.dyn.companyname.org = Public IP of Horizon DaaS dtRAM Gateway (A-Record)
view.companyname.org = view.dyn.companyname.org (CNAME 30 Second TTL)

If you are an avid user of DNS for cases like this you should be able to see why I did this.  During normal operations the users always connect to view.companyname.com in their client.  However,  in a disaster event you FLIP the CNAME to use the daas entry on the back end and when the client connects it’s completely transparent to them they are now on a DaaS cloud based desktop.  Pretty simply a clean and easy way to manage this step in the run book.

The Role of SSL Certificates For Clients

Something you want to make sure of in this setup so that all clients, both desktop and tablet based work, is that you need to use proper certificates.  You have really two options here to maintain the transparency to the user

  1. Install the SSL certificate for view.comnpanyname.com on all View Security Servers AND all the DaaS gateway servers.
  2. Use a wildcard certificate on all the servers

In either case the client is always connecting to “view.companyname.com” so when you flip between Horizon View Servers and DaaS gateway servers, you need the client to be able to authenticate the cert with the same name.  The goal here is to make it easy for the end user by not requiring them to change URL’s for their client.

Example Fail Over Video


Summary and Conclusions

My entire goal in life with this very extensive lab setup is simply to prove that you can use vCloud Air not only for IaaS, DaaS, and Disaster Recovery…..but most importantly you can pull all the parts together into one enterprise level architecture.  Instead of using vCloud Air Disaster Recovery on the desktops themselves save yourself time and effort.  Focus on the applications for Disaster Recovery along with the infrastructure and just leverage vCloud Air based desktops in Horizon DaaS to connect to those applications you have failed over.

VMware vCloud Connector is now free!

The hybrid cloud team at VMware is excited to announce the general availability of vCloud Connector 2.6.

VMware vCloud Connector links vSphere-based private and public clouds via a single interface, allowing you to manage them as a single hybrid environment. You can transfer virtual machines (VMs), vApps (collections of VMs with related resource controls and network settings), and templates from one vSphere-based cloud to another. You can also set up a content library to distribute and synchronize templates across clouds and extend a single Layer 2 network from your private data center to a vSphere-based public cloud.

With vCloud Connector 2.6, VMware has converged the core and advanced versions into a single free edition with access to all vCloud Connector features. Yes, advanced edition features such as content sync and data center extension are now free! A VMware vCloud Suite license or VMware vCloud Hybrid Service subscription is no longer required to take advantage of these advanced edition features.

We have also made significant improvements to the copy operation in this release:

  • Path Optimized Copy with Retry increases the resiliency of the vCloud Connector copy operation. We have redesigned the copy operation to include a transfer buffer, before the bits are sent out to the destination node, in the source vCloud Connector node. This design change ensures transfer continuity in case of network failures.
  • Pre-Copy Checks and validations improve reliability of the vCloud Connector copy.
  • Configurable Guest Customization settings are now available, including the option to preserve Guest OS settings.
  • A New Direct or Fenced network connection mode for deployment of any vApp to a destination vCloud Director-based cloud.

Overall, we have made substantial investments to improve the reliability and functionality of the product, reducing the on-ramp from onsite data centers to public clouds such as vCloud Hybrid Service.

Download the latest version of vCloud Connector here and read more about this release in the release notes here.

To learn more about our upcoming features and capabilities, follow the vCloud blog with your favorite RSS reader, or follow our social channels at @vCloud and Facebook.com/VMwarevCloud.

An In-Depth Look at vCloud Connector 2.0

By: Matt Sarrel

I recently started using the vSphere client to manage vCloud Connector (which according to VMware most people were doing anyway) – it’s a great alternative to the web interface I previously used for vCloud Connector.

You can still use vcloud.vmware.com to evaluate vCloud with a 90-day free trial, browse listings of service providers, and use resources like message boards, support, and instructional materials (such as documentation and tutorials).  The vCloud Connector 2.0 download is also hosted on the site.

It’s easy to use the vSphere Client to manage vCloud Connector:

  • Log into the vCloud Connector Server and then go to the Server and the vSphere Client tab.
  • From there, you’ll manage vCloud Connector through the traditional (Windows-only C#) vSphere Client’s Home page under the Solutions menu.

vCloud Connector is a great tool for linking private, public, and hybrid clouds.  I find it very powerful to be able to move applications, workloads, and templates between vClouds from a single management interface accessible via the vSphere client.  Built in and transparent features, like multi-part transfer, compression, and checkpoint restart makes transferring workloads reliable and easy.

The features that I’ve described above are part of the Core Edition of vCloud Connector.  There’s also an Advanced Edition of vCloud Connector that offers Content Sync and Datacenter Extension.  The ‘Core’ edition of VMware vCloud Connector is available to all current vSphere and vCloud Director customers as a free download – it is also included in the latest vSphere suites. To get support for the Core edition of vCloud Connector, you must have an active support contract for vSphere or vCloud Director. The ‘Advanced’ edition of vCloud Connector, which includes the Datacenter Extension and Content Sync features, is available exclusively as a part of the VMware vCloud Suites.

Content Sync lets you manage and publish a vSphere folder or a vCloud catalog and subscribe to it from another vCloud.  This is huge time saver because now you don’t have to manually copy folders and catalogs.  Any new or modified templates are automatically synchronized between subscribing catalogs.  Now an organization can have one large catalog across multiple clouds, which makes it easy to expand and move workloads between locations.

Datacenter Extension features extend private datacenter networks to public cloud networks, via a layer 2 connection over an SSL VPN tunnel.  This makes it possible to move workloads between clouds while retaining network settings (including MAC and IP addresses), so that other applications or users in the datacenter can continue to consume and use the workload.  Most importantly, other system management solutions can continue to manage the workload without any changes because network configuration remains the same.

This can all be done from within the vSphere Client, which makes managing multiple vClouds very accessible to virtualization administrators.

For future updates, be sure to follow @vCloud and @VMwareSP on Twitter!

Matthew D. Sarrel (or Matt Sarrel) is executive director of Sarrel Group, a technology product testing, editorial services, and technical marketing consulting practice based in New York City and San Francisco.  He currently writes for Enterprise Networking Planet, eWeek, PCmag.com, and GigaOM, blogs at TopTechDog, and publishes the Insights & Opportunities newsletter.  You can follow him on Twitter: @msarrel.

vCloud Director Hybrid Cloud Design Case Study

By: Chris Colotti

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

So all week I have been posting tidbits about the vCloud Director Hybrid cloud I have been building.  So what was my purpose for doing so?  Well I did it to make a couple of points of course the following is the final outcome formed into a bit of a case study that you can digest for a while.  The main reason I did this is that I feel we are still struggling with how to CONSUME the hybrid cloud model.   We’ve spent a lot of time architecting the vCloud Director implementations in both the public and private cloud space.  I decided I wanted to take a look at this from the consumer’s point of view.  Those people who would be wanting to come to those of you that are vCloud Director providers and help them understand HOW to use these public clouds.

Setting the Stage For vCloud Director Hybrid Clouds

So who are these consumers and users I am speaking about trying to help?  It can be any one of us but for the purpose of this case study I want to take two specific examples that fit many possible situations out there.

  • A new startup with NO Infrastructure
  • An enterprise that has reached the limit of their current Datacenter

In both cases the need is simple.  They both need to find new infrastructure without having to build it themselves.  In the case of both I am actually focussing on them not building more themselves, but rather leveraging the vCloud Providers out there.  They could consume in either a public cloud fashion, or a hosted private cloud fashion.  For purposes of this study let’s assume they have decided to go to public cloud providers.  I will play the role of the consumer as we continue forward.  I will also be taking the aspect of the second scenario above.  I have a datacenter, that’s met its limits of compute, memory, and storage.

Choosing your Providers

To be clear I am not suggesting where you go, but for my purposes here I happened to already have resources at two vCloud Public providers running vCloud Director 5.1 so I decided I was going to split my Infrastructure as a service (IaaS) between the two for some level of redundancy.  Also I personally think that makes you a smart IT person leveraging two different providers.  For my scenario as we know I have been using:

Obviously you can choose whomever you want, but in this case we are focussing on providers that are using vCloud Director 5.1 for it’s flexibility and simplicity to build your new organization   Once I have decided on the providers I am going to use the next steps are fairly simple and frankly are no different than you would do if you were building a physical datacenter, except now we are doing a Software Defined Datacenter, (SDDC).

Build your SDDC – Start with the Networking

Like any new datacenter you need to get the basic things configured.  As I have shown in previous posts, vCloud Director 5.1 provides a lot of power to the organization administrator….YOU.  The first order of business in my mind is the networking.  You want to design this separately for each site as you would for a new physical site.  Most all your traffic will leverage the Edge Gateway as well.

  • Decide on and configure your routed networks
  • Decide on and configure and isolated networks
  • Configure your SNAT rules
  • Configure basic outbound internet access firewall rules
  • Determine DHCP settings and Static IP Rules if any
  • Be sure to get from your provider various Public IP’s

Once you have gotten this figure out in your design of the two remote datacenters you can move forward.  It goes without saying you don’t want to cross networking subnets between sites or VPN will not work.  At this point you will also want to establish VPN connectivity between the sites and write the basic firewall rules for traffic to pass as you wish.  This will be important as you begin to stand up your infrastructure as a service.

Build your SDDC – Setup vCloud Connector, Import or Build New Templates

Here you can basically download and import the vCloud Connector Nodes into your two Public Clouds.  However, some providers are now building Multi-Tenant Nodes that you can simply leverage based on vCloud Connector 2.0.  If this is the case you only need to build your vCloud Connector Server hosted in one of your clouds, but maybe you want one in both.

Once you have this you can choose to move templates you already have in your current datacenter, or build fresh ones.  You can upload ISO images and just build new if you want to be sure things are setup fresh.  Either way you have the option so proceed as you wish.  So at this point, we have networking, templates, and site 2 site VPN connectivity established.  Now we just need to build out the Infrastructure we need to get started.

Build your SDDC – Active Directory

Like any new datacenter the first thing we probably need is localized Active Directory.  Assuming you have Active directory servers in your first datacenter you will want to make sure you setup new Sites and Services with the correct IP ranges.  Now I am now Active Directory expert, I am just trying to at least cover the basics.  Below you can see in my scenario I have set up the three sites, and also gone ahead and installed at least one Active Directory server in each of the new sites.  This will become the local authentication and DNS server for any new Windows infrastructure in that site.

vCloud Director

Once you have pre-configured Active Directory Sites and Services in your Physical Datacenter controllers you can install from templates and promote the ones in the other sites.  At this point you are ready to continue installing application servers, or other IaaS you want to add to your enterprise using your new vCloud Director Hybrid setup.  These can be things like Public DNS, Public SMTP servers, maybe even Desktops at some point although that’s neither tested, nor supported on vCloud Director.

Some Final Thoughts And Diagram

Although this has been a basic study of how you can leverage vCloud Director Hybrid Clouds to expand your enterprise, it should give you a foundation to start thinking about.  The diagram below is a much more expanded view of the possibilities you can reach to host many services in your new public vCloud Director Hybrid cloud.  Really the point is that this is just like building a new physical datacenter, only in most cases it’s much faster.  Of course as Network Virtualization and Storage Virtualization moves along this will only get better.  I will be presenting this on next weeks vBrown Bag as well so we can open up discussion.

vCloud Director

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.

How To Run vCloud Connector 2.0 Hosted With NAT

By: Chris Colotti

This is a repost from Chris’ personal blog, ChrisColotti.us.

As I have been building out this crazy vCloud Director Hybrid setup in a few of the public clouds I am using from VirtacoreStratogen, and the VMware Evaluation Cloud, I decided to try hosting all the vCloud Connector components in the various clouds.  One thing I remember from the vCloud Connector 1.0 days was the Server component was not happy behind a NAT.  That’s because the online web interface for vCloud.vmware.com tried to connect to the local IP address and it really just did now work behind NAT.  Now for me I am trying to use ALL online access to all these things so this is what I setup so far:

vCloud Connector Nodes Installed in:

  • Virtacore’s IAD Cloud
  • Virtacore’s LAX Cloud
  • VMware IAD Eval Cloud
  • Stratogen Cloud

Each of these nodes is on a “Public” network with external IP Addresses and firewall rules for the following ports:

  • 443
  • 5480 (Management)

vCloud Connector Server Installed in:

  • VMware IAD Eval Cloud
  • Same vApp as the Node

Now the firewall rules for the server are a little different and I did get an error on vCloud.vmware.com that it does need an additional port open but it does work 100% from the online vcloud.vmware.com portal

Firewall Rules for the Connector Server:

  • 443
  • 5480 (Management)
  • 80 for vCloud.vmware.com

NOTE:  These are not deployed from OVF with the VMXNET3 interface so for giggles be sure to remove the current interface and add a new one that is using VMXNET3 specifically by checking the “Show Network Adapter Type” box.

Configuring the vCloud Connector Server

Now something I was messing with was getting the vCloud Connector Server connected to the local vCloud Connector Node.  Due to the Edge Gateway I could not use the external IP on in the vCloud Connector Server config as you can see below.  I needed to use the local IP for the Node that’s in the same vCloud Director Cloud and in the same vApp as shown above.  I think there was some routing issue but it does not really matter since the Node and the Server are in the same network you can use the local IP address or local DNS for the connection.  The other nodes you can see are true external entries.

Once I did that the server is now connector to all 4 clouds through the online portal vcloud.vmware.com.

Migrating Templates

Now I was ready to move my Windows template from one cloud to Stratogen so I can continue to work on this expanded vCloud Director Hybrid Cloud setups.  As I continue with this experiment I will add more blog posts so people can really understand the power of how to use all this technology.

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.

Getting Started With vCloud – Intro to vCloud Connector and Other Resources

By: Matt Sarrel

I’ve been playing around with vCloud Connector 2.0 for a few weeks and I’d like to pass along some of the lessons I’ve learned and provide some tips for getting started.

First, I should explain what vCloud Connector is – vCloud Connector  is a virtual appliance that allows you to move workloads and virtual machines between clouds. These clouds could be private, public, or hybrid (a combination of the two). Private clouds need to run vSphere and vCenter Server, and public clouds need to run vCloud Director.

There are two components to vCloud Connector: vCloud Connector Server and vCloud Connector Node.  The server provides management features and you’ll probably want to host it with your management and maintenance server workloads. A node is a connection point for each cloud that is managed by the server. A typical configuration involves a single vCloud Connector Server and multiple vCloud Connector Nodes (one per cloud, organization, or vSphere instance). Think of this as the server is the gateway that controls the nodes as they prepare and shift workloads between clouds.

After servers and nodes are installed, you can log into each server individually, or you can get a free account on vcloud.vmware.com and manage all of your vCloud Connector servers through a single web based interface. You will need network access to each server as the portal redirects logins directly to the server. All communication between your machine, the servers, and the nodes is SSL encrypted. You may also choose to not use the portal and instead connect to the servers using vSphere Client 4.0, 4.1, or 5.0.

There is a lot of information about getting started available on vcloud.vmware.com. However, one of the best ways you can get hands-on testing and experience with vCloud  is by signing up for the VMware vCloud Service Evaluation. The vCloud Service Evaluation is an inexpensive option allowing users to get their feet wet in the public cloud arena (pricing starts at 4 cents an hour). This gives you the chance to experiment with connecting your internal vSphere environment to a public vCloud Director environment and moving workloads between them.

A great place to get started learning about all of this vCloud stuff is through the Learning & Support section on vCloud.VMware.com, as well as the New Users Guide to Using vCloud by VMware document.  This document provides detailed instructions on how to get started with the vCloud Service Evaluation.  Another must read document is the vCloud Connector User’s Guide which provides more detailed information on implementing and working with vCloud Connector.

Two additional valuable resources are the vCloud Community and the vCloud Playlist on VMwareTV.  I’ve found the vCloud playlist on YouTube to be particularly helpful as there are plenty of videos available for users to learn more about using vCloud, ranging from architecture overviews to detailed installation walk-throughs.

Speaking of detailed installation walk-throughs, my next post will show you how to install and configure vCloud Connector 2.0.

For future updates, be sure to follow @vCloud and @VMwareSP on Twitter!

Matthew D. Sarrel (or Matt Sarrel) is executive director of Sarrel Group, a technology product testing, editorial services, and technical marketing consulting practice based in New York City and San Francisco.  He currently writes for Enterprise Networking Planet, eWeek, PCmag.com, and GigaOM, blogs at TopTechDog, and publishes the Insights & Opportunities newsletter.  You can follow him on Twitter: @msarrel.

vCloud Connector 2.0 Now Available

By: Mathew Lodge

This is a repost from the RethinkIT blog. 

I’m pleased to announce that vCloud Connector 2.0 is now available for download! vCloud Connector (vCC) allows you to view, copy and manage VMs across vSphere, vCloud Director and any of the 180+ vCloud Powered and vCloud Datacenter IaaS cloud providers listed at vcloud.vmware.com. For more details on what’s in 2.0, see my earlier blog post.

There are two versions: vCloud Connector Core is a free download for anyone with vSphere, and vCloud Connector Advanced is free for anyone with the vCloud Suite. Here’s a summary of the differences:

vCloud Connector 2.0 Features Core Advanced
View, copy, move VMs and templates Yes Yes
User interface improvements Yes Yes
Transfer speed and reliability improvements Yes Yes
Cross-cloud search for VM or template by name Yes Yes
Automatic catalog synchronization across clouds No Yes
Migrate VM while maintaining IP and MAC addresses [VXLAN required] No Yes

vCloud Connector supports vSphere and vCloud Director 4.x and 5.x. It’s available from the “Drivers And Tools” tab of vSphere 5.1 and vCloud Director 5.1, or by following this link: vmware.com/go/downloadvcc.

For future updates, be sure to follow @vCloud and @VMwareSP on Twitter!

Updates to vCloud Suite Cloud Management Capabilities Announced at VMworld Barcelona

Photo via @teeglasgow

VMworld Barcelona kicked off today with a bang, with more than 8,000 attendees taking part in more than 250 unique breakout sessions and labs. During today’s keynote, Pat Gelsinger and Steve Herrod announced significant enhancements to VMware’s Cloud Management solutions – addressing cloud service provisioning, cloud operations management, and cloud business management.

Here’s a roundup of all the new cloud management capabilities that users can look forward to in the coming year:

vCloud Automation Center 5.1 – Multi-Cloud Infrastructure Provisioning 

Based on DynamicOps, VMware vCloud Automation Center 5.1 acts as a service governor, enabling policy-based provisioning across VMware-based private and public clouds, physical infrastructure, multiple hypervisors and Amazon Web Services. vCloud Automation Center 5.1 is integrated with vCloud Director to allow customers to leverage virtual datacenters comprised of the vCloud Suite’s software-defined services.

vFabric Application Director 5.0 – Provision Applications on Any Cloud

vFabric Application Director standardizes and accelerates how customers model and deploy multi-tier applications to any cloud – making it possible for customers to use the same blueprints to deploy packaged and custom applications across multiple virtual and hybrid cloud infrastructures (including Amazon EC2!).

vCenter Operations Management Suite 5.6 – Embedded, Integrated Cloud Operations Management

The vCenter Operations Management Suite applies patented analytics to integrated performance, capacity and configuration management – allowing customers to proactively enable service levels in hybrid cloud environments. vCenter Operations Management Suite 5.6 will also include vFabric Hyperic application-level monitoring to help customers proactively manage the health of business-critical applications like Microsoft SQL Server, Windows OS and more.

vCloud Connector 2.0 – Hybrid Cloud Portability

Significant enhancements to vCloud Connector will help make it possible to extend both networks and workload catalogs across hybrid cloud environments without the need for reconfiguring networks or settings when moving workloads. Check out more details from Mathew Lodge.

VMware IT Business Management Suite 7.5 – Enables Cloud Business Management

With a new IT benchmarking module that includes more than 3,500 metrics across 18 domains, IT organizations can compare their performance with industry and functional peers. The VMware IT Business Management Suite 7.5 also includes enhancements to its IT Finance Manager capabilities that will further automate and streamline the budgeting process.

In sum, according to Raghu Raghuram, executive VP of Cloud Infrastructure and Management at VMware, “VMware’s cloud management offerings fundamentally recast management for the cloud era, allowing customers to operate at cloud scale and begin to act as brokers of IT services to the business.”

For more updates from VMworld Barcelona, be sure to follow us on Twitter at @vCloud and @VMwareSP!

Announcing vCloud Connector 2.0 – One Network, One Catalog, One Cloud

By: Mathew Lodge

Today, VMware introduced vCloud Connector 2.0, the latest version of our tool for reliably and efficiently transferring virtual machines and data between vClouds. VMware’s vCloud platform is unique in that deploying applications and data to any cloud is a core capability. Rather than building an application so it can run in just one cloud, your application can run without changes in any vCloud, whether your own, or from one of our 160+ vCloud service providers.

vCloud Connector is the tool that simplifies the movement and management of applications and data between clouds. In version 2.0, we have made that process even simpler:

  • One network: move your application between clouds while retaining the same IP and Ethernet MAC address. Customers often told us that reconfiguring DNS and other network services and devices was time-consuming and error-prone. By using VXLAN to extend your Ethernet network into the public cloud, vCloud Connector can move the application without requiring DNS or other network reconfiguration – a great example of the power of software-defined networking.
  • One catalog: vCloud Connector can now automatically synchronize catalogs of virtual machines and applications (vApps) across clouds using a publish-and-subscribe mechanism. This is often used in software development and testing to automatically distribute the latest version of an application, for example. For customers with many applications and multiple clouds, this eliminates tedious and time-consuming manual catalog management.
  • One cloud: deployment of vCloud connector is now simpler and faster in multi-tenant clouds. The vCloud Connector node, which handles the transfers, can now be deployed once to manage all tenants in a cloud – in the previous version one node per tenant was required. We also improved the user interface and transfer capability based on your feedback.

In vCloud Conector 2.0, two editions will be available – vCloud Connector 2.0 Core (free download) and vCloud Connector 2.0 Advanced (included with VMware vCloud Suites).  Here’s a graphic that shows the capabilities of each version:

  • Datacenter Extension allows users to transfer workloads across clouds in a way that extends the logical boundaries of the datacenter. Datacenter Extension creates a Layer 2 VPN between private and public vClouds and retains the same IP address while moving workloads between the clouds. This allows the VM to continue to be consumed and managed by users, application and management solutions without any changes as if the VM never left the datacenter.

  • Manage a single content catalog across your entire cloud environment with a feature called Content Sync. Content Sync defines a ‘source’ catalog and to which other catalogs can subscribe. When new templates are added or changed in the source, the content will be securely and automatically copied to the subscribers. This allows for distributed teams to coordinate their efforts and ensure that everyone has a single, synchronized workload catalog across the cloud environment. 

With features like Datacenter Extension, Content Sync and multi-tenant node support, and an ecosystem of more than 160 service providers, vCloud Connector 2.0 enables cloud consumers to extend the logical boundaries of their datacenters, realizing the potential of hybrid cloud.

vCloud Connector 2.0 Core will be available as a free download and vCloud Connector Advanced will be available as a part of the VMware vCloud Suites later this year.

Learn more about vCloud Connector, the vCloud Suites, or browse the vCloud Service Provider ecosystem. Follow Mathew on Twitter @mathewlodge or follow the team for general updates on vCloud Connector and the vCloud ecosystem @vcloud and @VMwareSP.

VMware Provider Guide: Help Customers Move Workloads to the Cloud (Part 2)

In Part 1 of this series, we walked through accessing the vCloud Connector user interface via the vSphere client. In Part 2, we’ll break down how to access the interface over the Internet using a standard Web browser. 

If vCloud Connector is registered with vcloud.vmware.com, the vCloud Connector user interface can be accessed over the Internet using a standard Web browser. First, go to vcloud.vmware.com and log in using the vmware.com store account used to set up the vCloud Connector user interface during registration. 

To add a cloud, it should be made available to the system to allow workloads to be copied into it.  Simply select the name of the cloud registered with the vCloud Connector Server in the vCloud Connector window.  Enter the administrative username and password, and the cloud should be added to the cloud list, enabling workloads to be moved into the cloud when needed.


To move an existing workload from private, enterprise infrastructure into a public or hybrid cloud, select a workload such as a virtual machine, vApp, or template, and copy it to the cloud. 


Next, you need to identify the workload and the registered cloud to where it should be moved.  Specify a vApp template name and description, and note that if the source location is a vCloud Director cloud and the target is a vSphere cloud, the Source Catalog, cluster or host, resource pool, and datastore for the new instance need to specified. 


Once you’ve specified all of the information, copy the workload to the cloud.  A progress indicator will display the status, and the workload will be listed in the Completed section of the Tasks pane.  The original workload can be deleted from the source if desired.  Power on the virtual machines and vApps to enable them to be used. 


Whether you’re working through the vSphere client or a Web browser, VMware vCloud Connector makes it easy for customers of providers of vCloud Powered services to move their workloads to the cloud. As enterprises face the challenge of maintaining a flexible infrastructure capacity while containing costs, providers of vCloud Powered services have the advantage of offering secure clouds that work seamlessly with VMware-based cloud infrastructure. vCloud Connector makes this process painless by taking away the need for modifying existing infrastructure or applications.

Log on to Partner Central and download the whitepaper to learn more. Also be sure to follow us on Twitter at @vCloud and @VMwareSP  for the latest updates on vCloud Connector and vcloud.vmware.com.