15. Cloud Service Automation with IBM Tivoli Service Delivery Manager - Roles and Flow Clouduser Approver Cloudadmin Show existing server Approve request Use new server Request new project Cloud Administration Delivery ensurance Accounting & Reporting Self Service Ease of use and improved responsiveness and efficiency Workflow Manage the process for approval of usage Provisioning Automate provisioning of resources Monitoring Provide visibility of performance of virtual machines Metering and rating Track usage of resources
16.
17. IBM integrated software service management for cloud computing ESXi Hypervisor Resources Management Virtualization Managed to Service Automation Manager Applications Process Automation Engine Provisioning Manager** Discovery VM VM ESXi ® Hypervisor Hypervisor Hypervisor VM VM Windows Linux Directory Server VMware ® vSphere Server LDAP Server Service Management Managed from or Deployment Projects. Topologies Catalog Virtual Images & SW Stack Library Monitoring Manage Virtual Servers Provisioning actions Service Desk* Service Request Manager Usage & Accounting Monitor resources availability & usage Secure cloud management components Service Catalog Self-Service Virtual Server Management Solution Tailoring, if needed Role based access Admin User Dashboard IBM Tivoli Software IBM STG Software 3 rd Party Software Project based customizations Images/SW packages stacks Securing Virtualized Platform IBM ISS Software High Availability Enable Business Continuity Ease chargeback WebSphere CloudBurst Reporting IBM Hypervisors IBM Hypervisors LPAR LPAR LPAR x86 p z/VM IBM/OEM IBM Director Optional Resources Optional Hypervisor Hypervisor VM VM ISDM “ Blade Servers x” “ Storage” SAN
1 Service level agreement (SLA) 2 Independent software vendor (ISV) The graphic on this slide depicts the stages of the service lifecycle steps for testing, which include the following: The definition phase determines which services are offered in the catalog. During the design and definition phase these services are defined and made available. The is highly dependent on the requirements. Services can range from single resources to complex, full application stacks. During the offering phase, the services are approved by the governance team and then made available to end users. Once those services are available to end users, they can use the service portal or a process driven tool to request the service. Once requested, the available resources are examined and either scheduled for use immediately or reserved for use at a future point in time. Once approved for provisioning, the services are provisioned using automation and made available to end user. Once the end user is finished with the services, the resources are de-provisioned and put back into the resource pool. The resource pool is managed and governed by the administrator and as services are introduced or removed from the catalog they can be managed by the governance body.
TSAM is a component based on the Tivoli Process Automation Engine (TPAe), implementing a data model, workflows and applications for automating the management of IT services by using the notion of Service Definitions and Service Deployment Instances. The set of applications provided by TSAM can be collectively referred to as the TSAM Admin User Interface (UI) which provides access to all TSAM specific functionality. It should be noted here that this UI is not aimed at end users, since some level of detail knowledge about TSAM itself and about the concrete types of services automated using TSAM is required. The TSAM Admin UI is therefore more likely to be used by designers, operators and administrators of services. A more end user centered interface for requesting and managing IT services automated through TSAM can be provided by exposing certain functionality as service catalog offerings using the Service Request Management (SRM) component. By means of service offerings and offering UIs, the level of complexity exposed for any kind of service can be reduced to a level consumable by end users, hiding a lot of the details that are exposed by the TSAM Admin UI. TSAM and SRM rely on the CCMDB component in order to access information about resources in the managed datacenter. In addition, TSAM is also able to modify content of the CCMDB to reflect changes done by the execution of TSAM management processes. Finally, TSAM interlocks with Tivoli Provisioning Manager (TPM) to drive automated provisioning and deployment actions on the managed IT infrastructure. That is, while TSAM concentrates on the process layer of IT Service Management and hooks in automation into these processes, TPM can be used for really implementing these automated actions in the backend.
ISDM management stack is based on TSAM 7.2.1.1 plus Tivoli Monitoring, Tivoli Usage and Accounting Manager. TSAM is based on the Tivoli Process Automation engine (TPAe), which is the integration framework for the IBM Service Management portfolio. This permits expansion and integration with other important Service Management disciplines. TSAM traverses several Service Management disciplines, including Service Request Management, and Automated Provisioning with automation for some end-to-end scenarios that are the basis for Cloud Computing IaaS and PaaS. Because of the common framework however, full-blown implementations of the disciplines can be snapped in, and will integrate with TSAM and each other. TPAe is comprised of shared code and services that are employed by many different Service Management products. Install any one of them, like TSAM for example, and the shared code will be laid down. The installation of a second product will detect the presence of TPAe, and will install itself on top of the existing deployment, integrating with the first application. This ‘snap-in’ approach allows a step-wise approach to expansion of the solution, solving the most urgent problem first, and then expanding one discipline at a time. There is a shared user interface, a common data model, and a common workflow engine that allows workflows to traverse product boundaries seamlessly. Starting from a TSAM Cloud, a customer can expand in many directions as their strategy dictates. In fact, many of the components that TSAM uses internally are major products and technologies in their own right, and are the cornerstones of other Service Management disciplines. It uses Tivoli Provisioning Manager (TPM) as its provisioning engine. It uses Service Request Manager (SRM) to handle requests from the service catalog
Flow: Usage and Accounting Management provides key benefits for company satisfaction of IT Finance and lowering infrastructure costs
![Agenda ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)