<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>vCHS on vCO Team</title>
    <link>http://www.vcoteam.info/tags/vchs.html</link>
    <description>Recent content in vCHS on vCO Team</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 04 Feb 2014 00:00:00 +0000</lastBuildDate><atom:link href="http://www.vcoteam.info/tags/vchs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Getting started with vCO and vCHS</title>
      <link>http://www.vcoteam.info/articles/learn-vco/276-getting-started-with-vco-and-vchs.html</link>
      <pubDate>Tue, 04 Feb 2014 00:00:00 +0000</pubDate>
      
      <guid>http://www.vcoteam.info/articles/learn-vco/276-getting-started-with-vco-and-vchs.html</guid>
      <description>vCloud Hybrid Service (vCHS) is backed by vCloud Director. What does this mean? Well, it means that once you have defined 1 or more Virtual Data Centers, and VMware releases an updated vCD plug-in, you will have access to a vCloud Director Organization! Why is that good and what is the point of this post? Well, in short, this means you can use vCenter Orchestrator (vCO) to do some automation within your vCHS Virtual Data Centers!</description>
    </item>
    
  </channel>
</rss>
