This page is unlikely to be kept up-to-date. At the time of this update, the following vCO Documentation page provides documentation on the current release:
http://www.vmware.com/support/pubs/orchestrator_pubs.html
Current Release: vCenter Orchestrator 5.5.
VMware roadmaps are only communicated to customers / partners under NDA by VMware employees accredited to do so. This is not the case of the vCO Team members.
As of version 4.0.2, vCO has out-of-the-box support for the entire vCenter Server 4 API, as well as generic plug-ins that provide email, SSH, database, and XML APIs, allowing you to integrate with a large number of products. Also, vCO supports other plug-ins that are available as separate downloads, for example the Microsoft (Active Directory and WMI), and VMware Infrastructure 3.5 (vCenter 2.5) plug-ins.
VMware partners are also developing vCO plug-ins.
Initially, most customers who used vCO in production were running large datacenters. These are typically Service Providers, Financial and Industrial enterprise-level companies. With the increase in recent years of server capacity and of virtualization the user base has broadened within all sectors and company sizes.
vCO is owned by VMware. It is trademarked as "VMware vCenter Orchestrator".
There are a considerable number of pre-built actions that may be used to build your own workflows. The environment this table is taken from has the VC, VIM3, and Microsoft vmoapps installed:
Module: com.vmware.basic
com.vmware.basic
createDirectory
Description:
Create a directory structure on the VS-O server.
com.vmware.basic
getFileName
Description:
Strip directory from filenames.
Module: com.vmware.constants
com.vmware.constants
getDefaultCompanyName
Description:
Returns the company name.
