Posted on : 27 February 2013
Enabling cloud provider excellence by optimizing Service Orchestration In the modern era of cloud computing, expectations amongst business users, is unsurprisingly emulating consumer expectancy of virtually on-demand and highly optimized services. Although the timelines around the initial setup and ordering of cloud services varies depending on the level of complexity and service level associated with the service being required, the ongoing stopping, starting, scaling and changes to cloud services are expected to be swift and, more and more so, achieved while balancing regulatory compliance, business productivity needs and cost reduction.
Since there are numerous reference-able touch-points in the overall orchestration of these cloud services, the ODCA workgroups focused on mapping common service subscriber usage scenarios while defining a framework for cloud operators to improve service delivery. The Service Orchestration Master Usage Modelconsists of five high level groupings of service scenarios that make up the Cloud Service Life Cycle. Each cycle details the various tasks that make up a Compute Infrastructure as a Service cloud service and the different elements that make up the service catalog as well as what expectations to set with clients when ordering, changing, maintaining or decommissing services. Service Orchestration is required to link the various components that make up a CIaaS environment and build actionable relationships between the Solution Provider, Solution Receiver and Service Provider.
To grasp the full value of these Usage Models, it's important to understand how they interconnect together and provide ISV vendors (like ScienceLogic) a mechanism for communicating the benefits of their solution to those organizations building and consuming cloud services.