1. SERVICE ORCHESTRATION
Ryan Skipp
Deutsche Telekom / T-Systems GmbH
Catherine Spence
Intel Corporation

2. AGENDA
TOPIC
UM CORE
LEARNING
Service Orchestration:
Invoking and Operating Cloud based Services
• Usage Scenarios
• Service Catalogue
• Orchestration Processes
Considerations and take-aways from this UM
Forecast 2013 Service Orchestration U-Track| 2

3. SERVICE ORCHESTRATION UM BACKGROUND
ODCA Contributor organizations have created this UM to collaboratively
identify ways in how they agree cloud services should be Orchestrated, and to
then provide this as a clear guideline to Cloud Providers, ISV members, and to
share with the general community.
The Service Orchestration UM addresses and identifies:
1. Standardized Usage Scenarios (Service Lifecycle)
2. Interface requirements (API)
3. Key Performance Indicators
4. Categorization of service qualities in context of the UM
Forecast 2013 Service Orchestration U-Track| 3

4. UM CORE – KEY ELEMENTS
USAGE
SCENARIOS
Configure Service – Reserve Resources – Deploy Service – Change Service –
End/Delete Service – Return Resources to Available Pool
SERVICE
LIFECYCLE
Definition of clear service status’s, with associated activities
SERVICE
CATALOGUE
Definition of Service components and parameters for invocation
ORCHESTRATION
INTERFACES
API (REST based, )
GUI (Human IF, Reporting, Dashboards, Reviews, Control)
Forecast 2013 Service Orchestration U-Track| 4

5. SERV ORCH ARCH DIAGRAM
Forecast 2013 Service Orchestration U-Track| 5

6. PLAN Order (Compose, Request, Reserve)Scope demand and match it to services
BUILD Deploy, Track Status, Request Mgt
RUN
Start, Stop, Suspend, Data Collection, Admin and Remediation, Report, Capacity
Plan, Audit, Change
TERMINATE
End service, delete systems and data, and return resources to the available
resource pool, Comply with contract & regulatory requirements
UM CORE – MODEL & USAGE SCENARIOS
Forecast 2013 Service Orchestration U-Track| 6

7. Use REST based API’s
Consider and apply common standards and specifications for describing
services (e.g. OVF, TOSCA, CIMI, SPML, etc)
Categorise needs, categorise offerings, functionality and processes according
to Bronze, Silver, Gold & Platinum tiering
Define a formal Orchestration process, and Tooling as applicable, and define
accountability
KEY INDUSTRY ACTIONS (STANDARDS AND MORE)
API
STDS &
SPECIFICATIONS
CLASSIFY
SERVICES
ESTABLISH
ORCHESTRATION
FORMALLY
Forecast 2013 Service Orchestration U-Track| 7

8. Consumer has ownership of Service Orchestration
Process and Concept critical, tooling and automation
follows
Use open standard REST based API’s
Define your services and service qualities in detail
(consumer requirement side / provider offering side)
KEY TAKE-AWAYS FROM THIS UM
Forecast 2013 Service Orchestration U-Track| 8

9. Standardized
Response 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
Forecast 2013 Service Orchestration U-Track| 9

10. UM: Service Orchestration
From engagement to real adoption and
implementation
www.opendatacenteralliance.org
QUESTIONS
Forecast 2013 Service Orchestration U-Track| 10

11. Forecast 2013 Service Orchestration U-Track| 11
© 2013 Open Data Center Alliance, Inc. ALL RIGHTS RESERVED.