VMWORLD SITE

VMWORLD SITE
VMWORLD SITE

Wednesday 13 October 2010

Self Service and Workflow Automation for the Private Cloud Weds 13:30

John MacLean, Director, Product Management, VMware

Strategy is virtualization, automation and self-service
Self service drives efficient consumer data collection, is the basis for freedom of choice
Workflow is automation of the regular tasks

vCoud Request Manager interfaces with the vCloud Director vCloud API so that you can layer this over private clouds and compatible ISP cloud services
VMware Service Manager (ex EMC) - service desk, config & change, asst management, service request fulfilment to business users

Service Request Fulfilment:
- Hierarchical view of IT service catalogue - can include chargeback for each service
- When a request is created, data can be collected as per the design required - so can collect data from requestor based on tabs, collapsible sections, dates, drop downs etc.  Includes option to lease the selected resources
- Workflow generated through graphical interface and diagramming.  Many of the workflow tasks are hidden from the user (e.g. update inventory, email notifications).  Audit trailed, role based permissions.
- SLA responses are configurable - e.g. standard vApp driven VM can be minutes but custom can be weeks
- Tasks can call out or use connectors (e.g. VMware config mgr, EMC storage, 3rd party technology), write your own connectors.
- Connectors support discovery, events and push actions
- Connectors include vCloud Director

vCloud Request Manager (launched at VMWORLD Europe 2010)
- Adds workflow approval process to requests
  - Consumer (e.g. developer / trainer) selects an app from service catalogue
  - Feedsback to consumer when the app is up and running, post approval process
- Tracks software licence consumption
  - Need to associate licences with a vApp
  - Consumes and releases licences as apps are created and destroyed
- Policy Based Cloud Computing
  - Admin sets up blueprints that include chargeback etc.
  - Brings consistency through deployment of vApps (they're stacks!)

vApp templates can be exposed according to the permissions of the user

No comments: