Open Data Center Alliance Workgroups, Usage Models and Roadmap Structure


Published on

Learn about the Open Data Center Alliance Workgroups, Usage Models and Roadmap Structure from the perspective of the Alliance Technical Coordination Committee. This presentation was used in the Nov. 18, 2010 Alliance Webcast delivered by Howard Grodin, VP of Strategic Programs, Terrermark; Alliance Technical Coordination Committee Member, and Ravi Subranamiam, Intel Corporation; Alliance Technical Advisor.

For more information about the Open Data Center Alliance, visit You will also find the Webcast recording that accompanies this presentation there.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Open Data Center Alliance Workgroups, Usage Models and Roadmap Structure

  1. 1. Technical Coordination Committee & Workgroup Structure, Structure Roadmap and Usages Howard G di H d Grodin Ravi S Subramaniam VP Strategic Programs, Terremark Principal Engineer, CAP/EPI, Intel Technical Coordination Committee Technical Advisor, Open Data Center Member, Open Data Center Alliance Alliance © 2010 The Open Data Center Alliance ALL RIGHTS RESERVED The Open Data Center Alliance logo is a trademark of the Open Data Center Alliance
  2. 2. TOPICS  Open Data Center Alliance Objectives and Organization  Technical Coordination Committee (TCC) and Working Groups  U Usages and R d d Roadmap
  3. 3. CURRENT END-USER & ECOSYSTEM END-USER END USER VOICE FRAGMENTED AND DUPLICATED SDOs* & Vendors V d Forums Government * SDO = Standards Development Organization
  4. 4. WITH ALLIANCE - A TRANSFORMED ECOSYSTEM END USER VOICE AMPLIFIED COHERENT AND UNIFIED END-USER AMPLIFIED, SDOs* & Vendors Forums Open Data Center Alliance Open & Interoperability Consistent & Unified Requirements Requirements Alliance Principles: • Open Coherent Voice • Interoperable • Multi- Multi-sourced • Consistent • Coherent • Unified Government • * SDO = Standards Development Organization • Open Data Center Alliance will not create standards only provide requirements
  5. 5. OPEN DATA CENTER ALLIANCE GOALS FOCUS ON SEEDING OPEN ECOSYSTEM Identify critical usage models Address key IT pain points in the cloud transition Deliver roadmap of usage models that evolve over time Enable industry to deliver open solutions Enabling solution ecosystem in Next Generation Data Center and Cloud Computing that addresses end-user pain points and requirements end-
  6. 6. OPEN DATA CENTER ALLIANCE STRUCTURE SC TCC AND WORKGROUPS SC, Steering Committee Recommendation & Standard Approvals Organizations Liaisons Technical Coordination Committee External Technical Forums Technical Coordination Government Infrastructure Management Security Services & Ecosystem Members Members Members Members Members
  7. 7. FOCUS AREAS & WORKGROUPS • Design and build of DC IT Solution Cloud Creation Infrastructure (server, storage, network) Effective Management Management • Power, asset management & monitoring. & Operation Capacity, etc. Secure and Govern Security • And governance, compliance • Service definition, SLA Management, Cloud Use Services provisioning, service mappings & definition , Government, Environment & Government • Effi i Efficiency, Green computing, DC P li G ti Policy, and Ecosystem cloud models, green design, govt. policy Ecosystem Workgroups have international representation and we are working with Standards groups and other forums on liaisons
  8. 8. ROADMAP, USAGES AND ECOSYSTEM AN EXAMPLE INTERACTION MODEL Alliance Focus Eco System Focus Eco-System Open Data Center Ecosystem Programs Alliance Alliance Roadmap ISV OEM ISV OEM ISV OEM EU valued usages & ISV OEM roadmap to ecosystem (externally published) Usages •Reference architectures Docs •Platforms End-customers define •Solution stacks business functionality needed to deploy Other Industry cloud – output in form of Solutions Efforts Alliance documented roadmap & d d d (e.g. Open Source, System Workgroups usage documents Integrators etc.) Ecosystem non-binding feedback (as suggestions only!)
  10. 10. TECHNICAL COORDINATION COMMITTEE CHARTER • Primarily to coordinate Workgroup activities (both from a process and technical perspective) – including arbitrating on intra and inter WG usage-related issues • Formulate input and options for Steering Committee to act upon, for example: • Overall usage strategy • Roadmap recommendations • WG arbitration and resolution recommendations bit ti d l ti d ti • Engagement and opportunities with external forums/organizations • Own the overall usage agenda: • Drive agenda by developing the roadmap of usages • Use this roadmap and usage priorities to manage delivery of work products for each usage • Engage with partner organizations to reconcile and rationalize usage work • Educate others, including vendor community, on Alliance “technical activities” through mechanisms like Webcasts and presentations at key partner/other forums, etc o u s, etc. Note: Staffing of the TCC and WGs and nomination of WG chairs to be done by Steering Committee
  11. 11. WORKGROUPS
  12. 12. WORKGROUP STRUCTURE Workgroup Chair Facilitator / Secretary WG Members Attributes Alliance Contributors Active Special Interest Groups Formed or chartered if Regional Chapter and when required Industry Segment
  13. 13. WORKGROUPS OPERATIONS AND DECISIONS WG Primary Functions: • Encourage usage submission from any Alliance member via predefined template; WG reviews and validates for inclusion or modify/enhance as necessary for inclusion • WG directly responsible for constructing usages from practice and issues experienced by WG member organizations • Submission restricted to only Alliance members (Contributors and Adopters) WG Usage Development Process • WG decides process; Recommended - charter an informal study group per usage or identified topic – may be delegated to a regional cell where required WG Deliberations and Ratification Process: • WG tries for decision on a usage or proposed motion to be approved with full consensus – if not possible … • Pi t 10R i i Prior to 1.0 Revision: D i i on a usage or proposed motion d Decision d ti done with simple majority position ith i l j it iti (50%+) (and dissent positions recorded) • Post 1.0 Revision: Decision on a usage change/update or proposed motion adopted only with super majority (66%+)
  14. 14. WORKGROUPS USAGE DEFINITIONS Usage Definition and Format • Recommend Standard/Required Format with sufficient rigor • See published examples (usage examples provided at launch) • Usage versions < 1.0 for internal review and work product only; External publication at 1.0 version; publication will be periodically reviewed and revved post launch launch.
  16. 16. Reminder GOALS OF THE ALLIANCE USAGE MODEL ROADMAP  A public “one voice” statement by the Alliance of most valuable usage models and Alliance expectations for multivendor i t t ti f lti d interoperability bilit • Important and relevant • Bound to real end user implementation timeframes • Alliance Principles Valued  Guidance to vendors on desired open solutions  A framework to make the Alliance P i i l f kt k th Alli Principles “testable”  Used to guide internal organization planning and purchasing
  17. 17. ROADMAP PROCESS Alliance Initial I iti l Usage topics inputs from WGs and TCC U i i f WG d TCC Till Rev 0.5 WGs review roadmap  and document feedback WGs review roadmap and document feedback Released to Alliance non‐contributors for  Released to Alliance non‐ Rev 0.7 feedback Rev 0.95 Released to Steering Committee for ratification Rev 1.0 OFFICIAL RELEASE!!
  18. 18. ALLIANCE USAGE MODEL ROADMAP BY Open Data Center Alliance RELEASE CADENCE Initial Usage Models will be Released as part of 1.0 Roadmap H1 - 2011 Infrastructure Scale Out St S l O t Storage Proximity Based Storage Focus: Unified Networking • Long-term commitment with multi- Long- multi- Management year Roadmap. Policy Based P P li B d Power Dynamic W kl d D i Workload Management Placement Development: Security • 19 prioritized usage models culled Trusted Compute Pools Infrastructure Compliance from dozens of potential targets. Services Cloud On Boarding Common Provisioning Delivery • Workgroup development underway underway. Government & Ecosystem • Membership to approve 1.0 Cloud Models in Q1’11. Licensing Models NOTE: 0.5 directional roadmap shown; 1.0 POR roadmap in Q1 ‘11
  19. 19. USAGE ROADMAP BY ECOSYSTEM READINESS EXPECTATIONS 2011 2012 2013 2014 2013 2012 2011 Common Cloud On- On- Provisioning Licensing Boarding Models Cloud Models Dynamic Workload Infrastructure Placement Compliance Proximity Based Storage Policy Based Power Mgmt. Trusted Compute Pools Unified Networking Scale Out St Storage NOTE: 0.5 directional roadmap by launch; 1.0 POR roadmap in Q1 ‘11
  20. 20. USAGE MODELS
  21. 21. COLLATERAL TO BE DEVELOPED 1. 2 – 5 page summary of the usage “Provides a quick overview of the important aspects of the usage” 2. Detailed description of th usages f ll i standard 2 D t il d d i ti f the following t d d practices for defining usage models “Provides detailed definition of the context, actors, scenarios, use cases, alternate cases, expected outcomes etc” 3. Metrics “Define usage object es a d outco es in measureable te s e e objectives and outcomes easu eab e terms” 4. Benchmarks “A stretch goal at this time – framework, test cases and methods to independently validate solutions completeness and conformance to usage expectations”
  22. 22. USAGE MODEL SUMMARY: CLOUD ON-BOARDING Usage Open Solution Stack = Gaps in the Stack Applications Management & Operations VMM/OS Problem Moving an application into a public cloud is a complicated process that may require application redesign Statement and will require manual planning and provisioning. Once an application is instantiated in a particular public cloud, extracting it or moving it to another public cloud is difficult and non-standard. Solution Provide intermediation/migration/brokering tools that allow for easier Cloud On-Boarding; establish On Boarding; standards and federation models that allow for seamless On-Boarding. 2010 Usage • OnBoarding Data/Storage •OnBoarding Applications Scenarios • Store/Archive to Cloud • Instantiate single, simple application • Backup & Disaster Recovery • Instantiate complex application • Access and Retrieval • Extract application/data from Cloud 2010 Key Open ISV API’s Requirements Policy and Compliance Engines designed for simplicity Scalable and Available Management
  23. 23. CALL TO ACTION End-Users, Cloud Customers and Service Providers 1. Become a member at: p g 2. Apply for contributor membership to participate in the TCC and WGs – usage model topics and inputs welcome 3. Inform peers about the Open Data Center Alliance – create a stronger end user voice/position to Ecosystem 4. Attend 4 Att d members-only webcasts b l b t 5. Stay engaged with the Alliance Vendors 1. Watch for engagement opportunities in 2011
  24. 24. Q&A Become a member, join the conversation @opendatacenter
  25. 25. BACKUP
  26. 26. ALLIANCE ORGANIZATION Intel Steering Committee (Technical Advisor) ( ) Technical Marketing Coordination Committee Committee C itt Services PS RKGROUP Management Infrastructure WOR Security Government and Ecosystem