Real World IT Operations Integration Using vCO TECHMGT0930 Raju Koganty , VMware, Inc.

1. Real World IT Operations IntegrationUsing vCO TECHMGT0930 RajuKoganty, VMware, Inc.

2. This session may contain product features that are currently under development. This session/overview of the new technology represents no commitment from VMware to deliver these features in any generally available product. Features are subject to change, and must not be included in contracts, purchase orders, or sales agreements of any kind. Technical feasibility and market demand will affect final delivery. Pricing and packaging for any new technologies or features discussed or presented have not been determined. Disclaimer “These features are representative of feature areas under development. Feature commitments are subject to change, and must not be included in contracts, purchase orders, or sales agreements of any kind. Technical feasibility and market demand will affect final delivery.”

3. Facebook Search for VMware Partner Network TwitterSearch for VMware_Partners http://blogs.vmware.com/powerofpartnership/ Linkedin Search for VMware Partner Network Follow Us t Join the conversationGet the latest scoopBe a part of the network Subscribe to RSS Follow this event LIVE! #VMwarePEX2010 Help us help you! Please fill out the survey at the end of the course.

4. Agenda • Introduction • vCO plug-in architecture • Integrating out from vCO. • vCO plug-in development • Real world IT ops – BMC Remedy plug-in • Integrating into vCO • Real world IT ops – HP OO integrating with vCO • Q & A

5. What is Orchestration? • Talk to all sorts of devices • Configure for devices • Program Activities • Use Watch DVD TV: turn on Amp: turn on DVD: turn on TV: AUX input Amp: DVD input

6. VMware vCenter Orchestrator

7. vCO – Orchestrating the virtual world • Simple use case – IT request to create a VM with certain criteria • Get VM criteria • (OS type, CPU, memory) • Get requestor info • Create and place VM • Send an email Get VM criteria Get Requestor Info Resources available Provision VM Send Email

8. vCO – Orchestrating the virtual world and more • A little advanced – IT request to create a VM with • external authorization • Get VM criteria • (OS type, CPU, memory) • Get requestor info • Request authorization • Create and place VM • Send an email Get VM criteria Get Requestor Info Request authorization Resources available Provision VM Send Email

9. vCO – Workflows and plug-ins • Comes with a rich set of workflows. • A lot of the workflows are for VirtualCenter orchestration now. • Workflows are built on top of the plug-ins. • More plug-ins will be rolling out for various VMware products and hence more workflows . • If you’d like some of your product’s capabilities to be orchestrated, build a vCO plug-in. • You will enable users to build workflows that span VMware products and your products.

10. What are Plug-ins ? Plug-ins are code level extensions to the vCO platform (server). Plug-Ins provide new functionalities to the vCO platform. Plug-ins can be written by anyone, using the plug-in development kit. Other Plug-In features Plug-Ins extend the scripting engine by providing new objects. Plug-Ins extend the workflow palettes by providing new pre-defined scripts. Plug-Ins allow the creation of: New types Enumerated types Finders Plug-Ins Overview

11. Plug-in Structure • Plug-in is delivered as a dar file (Dunes archive) • Similar in structure to other JEE packaging formats • Vso.xml contains the meta information about the archive that is used by vCO. • War can be included that can act as the plug-in configuration webapp • Lib directory contains the jars with the functionality • Sample.dar • lib • *.jar • META-INF • Resources • *.hbm.xml • *.png • VSO-INF • vso.xml • Webapps • *.war

12. Vso.xml • Defines how the Orchestrator server interacts with the plug-in. • Must include reference to every type of object or operation that plug-in intends to expose to Orchestrator. • Components • Finders – rules that define how orchestrator locates and represents objects in the plug-in. • Inventory – objects that accessed using finders and displayed in the orchestrator client. • Scripting Objects - JavaScript object types that provide access to the objects, operations, and attributes in the plugged-in technology. Scripting objects define how Orchestrator accesses the object model of the plugged-in technology through JavaScript.

13. Plug-in Implementation • Implement IPluginAdaptor • Creates and initializes the plug-in factory below. • Returns the plug-in name. • Manages Events • Initializes configuration of the plug-in • Implement IPluginFactory • Finds objects – provides the implementation for finders in the vso.xml • Find related Objects – as defined in the relations in vso.xml • Executes plug-in commands if any. • Scripting Objects • Implement the objects as defined in the vso.xml that the plug-in will expose. • Singleton objects as defined in vso.xml will have one instance and can be used to implement the server interface if the plug-in interacts with an external server. • All other objects will acts as Java beans.

14. BMC Remedy integration use case • LCM • LCM with Change Tracking through BMC Remedy Task Management Change Request Automated Provisioning Intelligent Deployment Update CMDB VM Tracking Change Request Decommissioning

15. BMC APIs • BMC has a comprehensive set of API that allow one to programmatically manipulate their various modules. • Modules of interest in our case are : • ITSM (to submit change requests) • CMDB (to update the VM inventory) • Plan to integrate with ITSM 7.0 and CMDB 2.1 • Parts of the API are JNI based, and hence we chose to use pure Java api implementations only. • Arapi 7.5 is a pure java implementation and interacts with ITSM. • For CMDB we decided use the Web service API and so we created our stubs using Axis2.

16. Plug-in Details • Implemented Classes and methods (using BMC arapi) • BMCITSMPluginFactory • BMCITSMPluginAdaptor • ITSMServer (singleton) • submitChange • cancelChangeRequest • createVirtualMachineCI • modifyVirtualMachineCI • queryChange • findAssociatedTask • modifyTaskStatus • Data objects • ITSMChange, CMDBTask, VirtualMachineCI

17. Plug-in API in vCO client

18. Workflow using the plug-in

19. Workflow scripting box details

20. Integrating with vCO from outside • vCO provides a Web Services API that can be used to access and invoke Workflows through web services. • Essentially all workflows in vCO can be invoked from outside • More VMware products will be integrating with vCO and providing useful workflows. • As a result web service based integration will have access to all this growing library of workflows. • Essentially if there is a bigger system that automates/orchestrates processes and sits in the driver seat and virtualization is one aspect, then it can choose to integrate with vCO using the web-service api.

21. HP OO • HP Operations Orchestrator is one such bigger system that orchestrates a lot of HP products, does physical machine provisioning etc. • Example of a system that sits in the driver seat in an IT shop. • Now, if they’d like to add the capability to orchestrate VMware products, they could build individual connectors to each of VMware's products to orchestrate them. • Or they can just build the web service based integration to vCO and get access to the rich and growing set of workflows available within it. • And they are building a web service based integration that in essence would allow HP OO to orchestrate the VMware virtualization layer along with all the other stuff it does.

22. vCO Web Service API Details • The wsdl should be accessible at : • http://<Orchestrator_server>:8280/vmware-vmo-webcontrol/webservice • Generated stubs along with samples are available for download. • VSOWebControlProxy (the WS endpoint) provides API like: • Find • findForId • executeWorkflow • simpleExecuteWorkflow • getWorkflowTokenResult • getWorkflowTokenStatus • Complete API that allows one to access elements in the system, execute workflows and get workflow execution results.

23. Key Takeaways • vCO is a general purpose orchestration tool. • Comes with a compelling and growing set of workflows for VMware products. • One can build plug-ins and as a result provide workflows for their own products to work with the VMware virtualization layer. • Such workflows can span various IT systems like change management, billing etc. • Additionally, the rich library of workflows can be leveraged and executed from outside using the WS apis. • Try out vCO….it is free !!

24. Ready. Set. Go! Take Action • GO! Get Educated • Visit Partner University for information on partner programs and resources • Access to VMware Partner Exchange presentations • GO! Get Competent • Enroll in training and certification that counts toward earning competencies • GO! Register Your Deals to Earn More Margin • Visit Partner Central to learn about VMware’s registration programs

25. Any Questions?

26. Backup slides

27. Lifecycle Manager Workflow with Approvals from Remedy User Requests a VM in Lifecycle Manager Request Routed to Remedy for Approval VM created in vCenter Notify Remedy of Task Completion VM Available to User

28. User Requests a VM in Lifecycle Manager

29. Lifecycle Manager Workflow is started

30. Request Routed to Remedy for Approval

31. Request Approved In Remedy

32. VM Provisioning workflow Approved request picked from Remedy VM created through vCenter & Remedy Ticket Closed

33. VM created in vCenter

34. Notify Remedy of Task Completion

35. Remedy Ticket is Closed

36. VM Available to User