Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Forecast odcau4 100_eb


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Forecast odcau4 100_eb

  1. 1. SERVICE ORCHESTRATIONRyan SkippDeutsche Telekom / T-Systems GmbHCatherine SpenceIntel Corporation
  2. 2. AGENDATOPICUM CORELEARNINGService Orchestration:Invoking and Operating Cloud based Services• Usage Scenarios• Service Catalogue• Orchestration ProcessesConsiderations and take-aways from this UMForecast 2013 Service Orchestration U-Track| 2
  3. 3. SERVICE ORCHESTRATION UM BACKGROUNDODCA Contributor organizations have created this UM to collaborativelyidentify ways in how they agree cloud services should be Orchestrated, and tothen provide this as a clear guideline to Cloud Providers, ISV members, and toshare with the general community.The Service Orchestration UM addresses and identifies:1. Standardized Usage Scenarios (Service Lifecycle)2. Interface requirements (API)3. Key Performance Indicators4. Categorization of service qualities in context of the UMForecast 2013 Service Orchestration U-Track| 3
  4. 4. UM CORE – KEY ELEMENTSUSAGESCENARIOSConfigure Service – Reserve Resources – Deploy Service – Change Service –End/Delete Service – Return Resources to Available PoolSERVICELIFECYCLEDefinition of clear service status’s, with associated activitiesSERVICECATALOGUEDefinition of Service components and parameters for invocationORCHESTRATIONINTERFACESAPI (REST based, )GUI (Human IF, Reporting, Dashboards, Reviews, Control)Forecast 2013 Service Orchestration U-Track| 4
  5. 5. SERV ORCH ARCH DIAGRAMForecast 2013 Service Orchestration U-Track| 5
  6. 6. PLAN Order (Compose, Request, Reserve)Scope demand and match it to servicesBUILD Deploy, Track Status, Request MgtRUNStart, Stop, Suspend, Data Collection, Admin and Remediation, Report, CapacityPlan, Audit, ChangeTERMINATEEnd service, delete systems and data, and return resources to the availableresource pool, Comply with contract & regulatory requirementsUM CORE – MODEL & USAGE SCENARIOSForecast 2013 Service Orchestration U-Track| 6
  7. 7. Use REST based API’sConsider and apply common standards and specifications for describingservices (e.g. OVF, TOSCA, CIMI, SPML, etc)Categorise needs, categorise offerings, functionality and processes accordingto Bronze, Silver, Gold & Platinum tieringDefine a formal Orchestration process, and Tooling as applicable, and defineaccountabilityKEY INDUSTRY ACTIONS (STANDARDS AND MORE)APISTDS &SPECIFICATIONSCLASSIFYSERVICESESTABLISHORCHESTRATIONFORMALLYForecast 2013 Service Orchestration U-Track| 7
  8. 8. Consumer has ownership of Service OrchestrationProcess and Concept critical, tooling and automationfollowsUse open standard REST based API’sDefine your services and service qualities in detail(consumer requirement side / provider offering side)KEY TAKE-AWAYS FROM THIS UMForecast 2013 Service Orchestration U-Track| 8
  9. 9. StandardizedResponse ChecklistsAccelerate TTMShared PracticesDrive ScaleStreamlinedRequirementsAccelerate AdoptionAvailable to Members at: www.opendatacenteralliance.orgURL for Public content: www.opendatacenteralliance.orgINFORMATION AND ASSETSForecast 2013 Service Orchestration U-Track| 9
  10. 10. UM: Service OrchestrationFrom engagement to real adoption andimplementationwww.opendatacenteralliance.orgQUESTIONSForecast 2013 Service Orchestration U-Track| 10
  11. 11. Forecast 2013 Service Orchestration U-Track| 11© 2013 Open Data Center Alliance, Inc. ALL RIGHTS RESERVED.