ODCA Service Orchestration Use Cases and Customer Requirements
-
Upload
open-data-center-alliance -
Category
Technology
-
view
105 -
download
2
description
Transcript of ODCA Service Orchestration Use Cases and Customer Requirements
SERVICE ORCHESTRATION
Ryan SkippT-Systems GmbH
AGENDA
TOPIC
UM CORE
LEARNING
Title: Service Orchestration UM v2.0Subtitle: A Usage Model overview
• High level process• Core Architecture• KPI’s for Service Orchestration• Service Lifecycle management
ODCA Flash Seminar | 2
Important processes, requirements and considerations in orchestration of cloud services
UM BACKGROUND
Cloud Service Orchestration v2.0
The Service Orchestration v2.0 UM addresses and identifies:
1. Important Usage Scenarios to accommodate in an Orchestrator2. The Architecture and elements of the Orchestrator3. API and Interface planning4. KPI definitions for Service Orchestration
ODCA Flash Seminar | 3
UM CORE – KEY ELEMENTS
five high-level groupings of usage scenarios based on the orchestration tasks that cloud subscribers execute, which also map closely to the industry concepts of Install, Move, Add, Change, and Delete
The orchestration process itself must belong to the cloud consumer, who has overall responsibility for triggering requests and paying for services. However, the orchestration systems and tooling can be provided by the consumer, or one of the cloud provider parties. The orchestration process from the cloud provider side can also initiate a process or processes in the cloud consumer side: for example, notification or alerting.
With REST, there is the concept of resources and collections. A resource is a typed object with properties, methods, and associations with other objects. A collection is a directory or group of resources. Since resources are addressed through Uniform Resource Identifiers (URIs), the expectation is for the cloud provider to use conventional URI design to publish APIs
KPIs are control tools designed to allow the measurement of the following aspects of a service:1. Progress2. Compliance3. Effectiveness4. Efficiency
ODCA Flash Seminar | 4
Usage Scenarios
Architecture
API & Interfaces
KPI’s
DIAGRAM: ORCHESTRATION USAGE SCENARIOS
ODCA Flash Seminar | 5
DIAGRAM: SERVICE ORCHESTRATOR ARCHITECTURE
ODCA Flash Seminar | 5
Service Availability
Speed & Timeliness
Accuracy
Compliance
ORCHESTRATION KPI’S
ODCA Flash Seminar | 6
Financial
Service Satisfaction
Service Execution Incidents
Define open standards for advertisement of cloud services to cloud brokers
Define the key integration points between cloud service providers and service consumers, and the minimum expected functionality from each side, to enable open standards based automation between them
Define standards for encapsulating catalog entries for advertisement, all the way from IaaS through PaaS, to SaaS levels.
KEY INDUSTRY ACTIONS (STANDARDS AND MORE)
Standards
Pre-requisites
Catalogue Definitions
ODCA Flash Seminar | 7
Make sure you understand Orchestration, when establishing Cloud services and selecting partners
Get the responsibilities and ownership for key functions clearly defined up front
Make sure your environment can scale over time – towards including alternate clouds and partners
Define key measures up front for orchestrating services, and monitor their achievement over time
KEY TAKE-AWAYS FROM THIS UM
ODCA Flash Seminar | 8
UM: Service OrchestrationFrom engagement to real adoption and implementation
www.opendatacenteralliance.org
QUESTIONS
ODCA Flash Seminar | 10
StandardizedResponse Checklists
Accelerate TTM
Shared Practices Drive Scale
Streamlined Requirements
Accelerate Adoption
Available to Members at: www.opendatacenteralliance.org
URL for Public content: www.opendatacenteralliance.org
INFORMATION AND ASSETS
ODCA Flash Seminar | 9