IBM's SmartCloud Orchestrator provides end-to-end automation of cloud service delivery through workload orchestration, resource orchestration, and service orchestration. It integrates with existing data center tools and processes using open standards. The Orchestrator includes content types like software bundles, virtual images, and patterns to automate multi-tier application deployments. It also allows custom orchestration operations through actions, user interfaces, and service offerings.
Compute Domain: Hypervisors (VMware, KVM, OpenStack, PowerVM, etc) Storage Domain: Storage Provisioning, Backup and Restore Network Domain: Provisioning and Configuring network devices (firewall, routing, switches, etc) IT Asset Management: Deliver repeatable business outcomes by managing both traditional applications and the intelligent IT enabled assets that support them Change Management: Defining standard, automated change procedures that ensure integrity of existing infrastructure while supporting business agility Service Desk: Improve quality of service and business resiliency by linking service requests with asset and change management, Single service desk tool for service requests & approval workflows.
09/30/11 09/30/11
It’s not only important to cover the structural model of a cloud service – “deployment only” is not sufficient. Think about setting up a complex system, eg. SAP. It takes a long time to set it up, but it is an equally big challenge to maintain and operate it! TOSCA allows to have built-in “build- and management plans” that help to set up, operate and maintain and tear down the service. Those “management plans”, which are operating directly on the topology description, are done by experts of the service – sticking to my example: SAP knows best how to install, maintain and operate an SAP system, so they will prescribe these plans. This helps each party - Cloud Provider and Cloud Service Provider – to focus on their key aspects, because it decouples cloud infrastructure from cloud content. Bottomline: TOSCA allows to describe a service in a holistic way and throughout the whole lifecycle File Name Here.ppt
It’s not only important to cover the structural model of a cloud service – “deployment only” is not sufficient. Think about setting up a complex system, eg. SAP. It takes a long time to set it up, but it is an equally big challenge to maintain and operate it! TOSCA allows to have built-in “build- and management plans” that help to set up, operate and maintain and tear down the service. Those “management plans”, which are operating directly on the topology description, are done by experts of the service – sticking to my example: SAP knows best how to install, maintain and operate an SAP system, so they will prescribe these plans. This helps each party - Cloud Provider and Cloud Service Provider – to focus on their key aspects, because it decouples cloud infrastructure from cloud content. Bottomline: TOSCA allows to describe a service in a holistic way and throughout the whole lifecycle File Name Here.ppt