Attention vCO users, developers and Administrators! We have just added a new section to the vCO Team Website for Frequently Asked Questions in the format of Q & A. We've broken the section out into multiple Categories and begun populating the categories with some common Questions we have encountered over the last few years. If you're on an RSS reader, the Q & A section is separate . Stop in and take a look.

They do a combination of the following: The run some of the library high level workflows. Automate vCenter tasks, such as chaining repetitive operations in workflows. For example, automating the VM provisioning process. Integrate VMware operations with their databases, change management and ticketing systems. Create high-level workflows that involve different approvals and operations from different teams. Provision the virtual infrastructure. For example adding hosts, creating and configuring clusters and resource pools.

vCO allows you to design and run IT process automation workflows. For example, you can run high-level process workflows, such as a complex provisioning process that includes several technical sub-workflows, such as a workflow to clone a vCenter virtual machine. Some basic ideas include: Get all VMs for a specified Folder/ResourcePool/Datacenter and then: Cleanup all the old snapshots Disconnect all removable media Migrate VM Templates from host that is going to be put into Maintenance mode The possibilities are endless.

vCenter Orchestrator.

This is a list of what a plug-in can provide, not all the features are mandatory. Objects and methods on the orchestrated technology. A hierarchical inventory of these objects. Choosers and pickers to be able to select these objects. Events on object states and gauges. An API documentation for using these. Scripts for function level functionality. Workflows for higher level operations. Transparent session management. Object caching. Object persistence.

vCO provides an orchestration platform that runs on top of scripted operations (vCO actions) and programs (vCO plug-ins). This platform provides the following facilities: A stateless workflow engine server. All the process flows and data flows are stored in a database. Centralization. No scripts scattered across all the orchestrated entities. Checkpointing. The ability to resume a workflow from the point at which it stopped in case of system maintenance or failure.

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.

Let the VMware customers know that vCenter includes a powerful Orchestration platform. Aggregate existing vCO public information from different sources. Fill the gaps with providing some unique articles, tutorials, hints. Create a community of specialists.

Java is the language used to develop plug-ins. You can bridge Java to other technologies using standard communication interfaces and bridge technologies.

Javascript. Specifically, vCO provides a Mozilla Rhino implementation. Jacascript is used for vCO actions and within vCO scriptable boxes.