This session was about the challenges being faced by organizations to efficiently orchestrate a cross sytem environment. The focus was to keep it simple and let the vCO orchestrate what your company has in house.
The session began with a talk about plugins available for vCO. There is vCloud service provisioning with vCAC and vFabric app director. The provisioning also works with vCO for IT process automation as well as 3rd party integration with the helpdesk and CMDB.
A new feature being introduced is automated remediation for vCOPS. Event based triggers are available (AMQP & SNMP) that will act upon signals received and a pre defined workflow/task will commence. Further direct API calls and indirect integration is also available.
From an integration standpoint there is now North & Sound bound integration. This seems fancy but the stuff is very straightforward.
North bound integration is for vCO workflows that get called by other systems – e.g. vSphsere web client, Cloud portal, blocking task in vCD etc.
Sound bound integration is for vCO workflows that call other systems – e.g. Physical infrastructure like servers & storage, vSphere, vCD, legacy apps etc.
VMware now offers vCO plugin SDK that can be used to develop own custom plugins – the SDK consists of Eclipse add-on for VCO plugin, command line utilities, and best practice guide.
Some best practice rules for vCO
- Avoid programming
Use rich workflow library
- Creative copy paste approach
- use debugging option
- use resume from failure
- use Out of the Box HA
- use version control
- use auto generate WF
- generate WF documentation
vCO also works with powershell scripts so they can be integrated for further benefits. From version vSphere 5.5, vCO can be setup to work in a cluster mode – clustering + HA
Currently VMware offers a lot of plugins as part of the vCO software. Take maximum advantage of it to learn more about vCO or follow Hands on Lab HOL-PRT-1304