Technical Coordination Technical Coordination Committee & Workgroup Structure Roadmap and UsagesStructure, Roadmap and Usages

H d G di SHoward GrodinVP Strategic Programs, Terremark Technical Coordination Committee Member, Open Data Center Alliance

Ravi SubramaniamPrincipal Engineer, CAP/EPI, IntelTechnical Advisor, Open Data Center Alliance

© 2010 The Open Data Center Alliance ALL RIGHTS RESERVEDThe Open Data Center Alliance logo is a trademark of the Open Data Center Alliance

TOPICS Open Data Center Alliance Objectives and

Organization Technical Coordination Committee (TCC) and

Working Groups U d R d Usages and Roadmap

CURRENT END-USER & ECOSYSTEMEND USER VOICE FRAGMENTED AND DUPLICATEDEND-USER VOICE FRAGMENTED AND DUPLICATED

SDOs* SDOs* && V dV d& &

ForumsForumsVendorsVendors

GovernmentGovernment

* SDO = Standards Development Organization

WITH ALLIANCE - A TRANSFORMED ECOSYSTEMEND USER VOICE AMPLIFIED COHERENT AND UNIFIEDEND-USER VOICE AMPLIFIED, COHERENT AND UNIFIED

SDOs* SDOs* && VendorsVendors& &

ForumsForumsVendorsVendors

Open Data Center AllianceOpen Data Center Alliance

Consistent & UnifiedConsistent & UnifiedRequirementsRequirements

Open & InteroperabilityOpen & InteroperabilityRequirementsRequirements

Coherent VoiceCoherent Voice

Alliance Principles:Alliance Principles:•• OpenOpen•• InteroperableInteroperable•• MultiMulti--sourcedsourced

GovernmentGovernment

•• ConsistentConsistent•• CoherentCoherent•• UnifiedUnified

• * SDO = Standards Development Organization• Open Data Center Alliance will not create standards only provide

requirements

OPEN DATA CENTER ALLIANCE GOALS FOCUS ON SEEDING OPEN ECOSYSTEMSEEDING 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 Enabling solution ecosystem in Next Generation Data Center and Cloud Computing that addresses endComputing that addresses end--user pain points and requirementsuser pain points and requirements

OPEN DATA CENTER ALLIANCE STRUCTURESC TCC AND WORKGROUPSSC, TCC AND WORKGROUPS

Steering Committee

StandardStandardRecommendation &Recommendation &

Technical Coordination Committee

Standard Standard OrganizationsOrganizations

External External TechnicalTechnical

ApprovalsApprovals

LiaisonsLiaisons

Technical Technical ForumsForums

Technical CoordinationTechnical Coordination

InfrastructureInfrastructure ManagementManagement SecuritySecurity ServicesServicesGovernment Government

&&EcosystemEcosystem

MembersMembers MembersMembers MembersMembers MembersMembers MembersMembers

FOCUS AREAS & WORKGROUPS• Design and build of DC IT Solution

(server, storage, network)InfrastructureCloud Creation

Effective • Power, asset management & monitoring.

Capacity, etc.ManagementEffective Management & Operation

• And governance, complianceSecuritySecure and Govern

• Service definition, SLA Management, provisioning, service mappings & definitionServices

Effi i G ti DC P liGovernment

Cloud Use

Government, • Efficiency, Green computing, DC Policy,

cloud models, green design, govt. policy Government

and Ecosystem,

Environment & Ecosystem

Workgroups have international representation and we are Workgroups have international representation and we are working with Standards groups and other forums on liaisonsworking with Standards groups and other forums on liaisons

ROADMAP, USAGES AND ECOSYSTEMAN EXAMPLE INTERACTION MODEL

Alliance Focus Eco System Focus

Open Data Center Alliance

Ecosystem Programs

Alliance Focus Eco-System Focus

EU valued usages & roadmap to ecosystem

OEMISVISV

ISVISV

OEMOEM

OEM

Alliance Roadmap

roadmap to ecosystem (externally published)

•Reference architectures•Platforms

UsagesDocs

•Solution stacksEnd-customers define business functionality needed to deploy cloud – output in form of d d d & Alliance

Other Industry Solutions Efforts

documented roadmap & usage documents

Alliance

Workgroups(e.g. Open Source, System

Integrators etc.)

Ecosystem non-binding feedback (as suggestions only!)

TECHNICAL COORDINATION TECHNICAL COORDINATION COMMITTEE (TCC)

TECHNICAL COORDINATION COMMITTEE• Primarily to coordinate Workgroup activities (both from a process and technical

perspective) – including arbitrating on intra and inter WG usage-related issues

CHARTER

• Formulate input and options for Steering Committee to act upon, for example:• Overall usage strategy• Roadmap recommendations

WG bit ti d l ti d ti• WG arbitration and resolution recommendations• Engagement and opportunities with external forums/organizations

• Own the overall usage agenda: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 workEngage 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

WORKGROUPSWORKGROUPS

WORKGROUP STRUCTURE

WorkgroupWorkgroup

ChairChair

Facilitator / SecretaryFacilitator / Secretary

WG MembersWG Members

Alliance ContributorsAlliance Contributors ActiveActive

AttributesAttributes

Regional ChapterRegional Chapter

Special Interest GroupsSpecial Interest GroupsFormed or Formed or chartered if chartered if Regional ChapterRegional Chapter

Industry SegmentIndustry Segment

and when and when requiredrequired

WORKGROUPSOPERATIONS AND DECISIONSWG 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

OPERATIONS AND DECISIONS

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 …P i t 1 0 R i i D i i d ti d ith i l j it iti• Prior to 1.0 Revision: Decision on a usage or proposed motion done with simple majority position (50%+) (and dissent positions recorded)

• Post 1.0 Revision: Decision on a usage change/update or proposed motion adopted only with super majority (66%+)

WORKGROUPSUSAGE DEFINITIONS

Usage Definition and Format

USAGE DEFINITIONS

• 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 launchversion; publication will be periodically reviewed and revved post launch.

USAGE ROADMAPUSAGE ROADMAP

GOALS OF THE ALLIANCE USAGE MODEL ROADMAPReminderReminder

A public “one voice” statement by the Alliance of most valuable usage models and Alliance

t ti f lti d i t bilitexpectations for multivendor interoperability• Important and relevant• Bound to real end user implementation timeframes• Alliance Principles Valued

Guidance to vendors on desired open solutions A f k t k th Alli P i i l A framework to make the Alliance Principles

“testable” Used to guide internal organization planning Used to guide internal organization planning

and purchasing

ROADMAP PROCESS

AllianceAlliance

I iti lI iti l U i i f WG d TCCU i i f WG d TCCInitialInitial Usage topics inputs from WGs and TCCUsage topics inputs from WGs and TCC

Till Rev 0.5Till Rev 0.5 WGs review roadmap and document feedbackWGs review roadmap and document feedbackTill Rev 0.5Till Rev 0.5 WGs review roadmap  and document feedbackWGs review roadmap  and document feedback

Rev 0.7Rev 0.7 Released to Alliance Released to Alliance nonnon‐‐contributorscontributors for for feedbackfeedbackfeedbackfeedback

Rev 0.95Rev 0.95 Released to Steering Committee for ratificationReleased to Steering Committee for ratification

Rev 1.0Rev 1.0 OFFICIAL RELEASE!!OFFICIAL RELEASE!!

ALLIANCE USAGE MODEL ROADMAPBY Open Data Center Alliance RELEASE CADENCE

H1 H1 -- 2011 2011

InfrastructureInfrastructure

Initial Usage Models will be Initial Usage Models will be Released as part of 1.0 RoadmapReleased as part of 1.0 Roadmap

S l O t StS l O t St Focus:Focus:

ManagementManagement

Proximity Based StorageProximity Based Storage

D i W kl dD i W kl d

Scale Out StorageScale Out Storage

Unified NetworkingUnified Networking

P li B d PP li B d P

Focus:Focus:•• LongLong--term commitment with multiterm commitment with multi--

year Roadmap. year Roadmap.

Development:Development:•• 19 prioritized usage models culled 19 prioritized usage models culled

from dozens of potential targets. from dozens of potential targets. SecuritySecurity

Dynamic Workload Dynamic Workload PlacementPlacement

Trusted Compute PoolsTrusted Compute Pools

Policy Based Power Policy Based Power ManagementManagement

Infrastructure ComplianceInfrastructure Compliance

DeliveryDelivery•• Workgroup development underwayWorkgroup development underway

ServicesServices

Common ProvisioningCommon ProvisioningCloud On BoardingCloud On Boarding

•• Workgroup development underway.Workgroup development underway.•• Membership to approve 1.0 Membership to approve 1.0

in Q1’11.in Q1’11.Government & EcosystemGovernment & Ecosystem

Licensing ModelsLicensing Models

Cloud ModelsCloud Models

NOTE: 0.5 directional roadmap shown; 1.0 POR roadmap in Q1 ‘11

USAGE ROADMAP BY ECOSYSTEM READINESS EXPECTATIONSBY ECOSYSTEM READINESS EXPECTATIONS

20122012 20142014 2012201220132013 20132013

Licensing Licensing ModelsModels

Licensing Licensing ModelsModels

Cloud OnCloud On--BoardingBoardingCloud OnCloud On--BoardingBoarding

20112011 20112011Common Common

ProvisioningProvisioningCommon Common

ProvisioningProvisioning

Cloud ModelsCloud ModelsCloud ModelsCloud Models

Dynamic Dynamic WorkloadWorkloadDynamic Dynamic WorkloadWorkload InfrastructureInfrastructureInfrastructureInfrastructure

Policy Based Policy Based Power Mgmt.Power Mgmt.Policy Based Policy Based Power Mgmt.Power Mgmt.

Workload Workload PlacementPlacementWorkload Workload PlacementPlacement

Proximity Proximity Based StorageBased Storage

Proximity Proximity Based StorageBased Storage

Infrastructure Infrastructure ComplianceCompliance

Infrastructure Infrastructure ComplianceCompliance

Trusted Compute Trusted Compute Trusted Compute Trusted Compute

Unified Unified NetworkingNetworking

Unified Unified NetworkingNetworking

PoolsPoolsPoolsPools

Scale Out Scale Out StSt

Scale Out Scale Out StSt

NOTE: 0.5 directional roadmap by launch; 1.0 POR roadmap in Q1 ‘11

StorageStorageStorageStorage

USAGE MODELSUSAGE MODELS

COLLATERAL TO BE DEVELOPED1. 2 – 5 page summary of the usage

“Provides a quick overview of the important aspects of the usage”

2 D t il d d i ti f th f ll i t d d2. Detailed description of the usages following standard practices for defining usage models“Provides detailed definition of the context, actors, scenarios, use cases, alternate cases, expected outcomes etc”

3. Metrics“Define usage objectives and outcomes in measureable terms”e e usage object es a d outco es easu eab e te s

4. Benchmarks“A stretch goal at this time – framework, test cases and methods to independently validate solutions completeness and conformance to usageindependently validate solutions completeness and conformance to usage expectations”

USAGE MODEL SUMMARY: CLOUD ON-BOARDINGUsage

Open Solution Stack = Gaps in the Stack= Gaps in the Stack

Management & OperationsManagement & Operations

VMM/OSVMM/OS

ApplicationsApplications

Problem Statement

Moving an application into a public cloud is a complicated process that may require application redesign 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 Solution Provide intermediation/migration/brokering tools that allow for easier Cloud On Boarding; establish standards and federation models that allow for seamless On-Boarding.

2010 Usage Scenarios

• OnBoarding Data/Storage• Store/Archive to Cloud• Backup & Disaster Recovery

•OnBoarding Applications• Instantiate single, simple application• Instantiate complex applicationBackup & Disaster Recovery

• Access and RetrievalInstantiate complex application

• Extract application/data from Cloud

2010 Key Requirements

Open ISV API’s Policy and Compliance Engines designed for simplicityScalable and Available Management

CALL TO ACTIONEnd-Users, Cloud Customers and Service Providers1. Become a member at: www.opendatacenteralliance.orgp g2. Apply for contributor membership to participate in the TCC

and WGs – usage model topics and inputs welcome3. Inform peers about the Open Data Center Alliance – create

a stronger end user voice/position to Ecosystem4 Att d b l b t4. Attend members-only webcasts5. Stay engaged with the Alliance

Vendors1. Watch for engagement opportunities in 2011

Q & AQ & ABecome a member, join the conversation

www.opendatacenteralliance.org

@opendatacenter

www.facebook.com/opendatacenter

www.linkedin.com/groups?mostPopular=&gid=3664896

BACKUPBACKUP

ALLIANCE ORGANIZATION

Steering CommitteeSteering Committee IntelIntel(Technical Advisor)(Technical Advisor)

Marketing Marketing CommitteeCommittee

Technical Technical Coordination Coordination C ittC itt

( )( )

PS

PS

CommitteeCommittee

ServicesServices

RK

GR

OU

PR

KG

RO

UP

Infrastructure Infrastructure

ManagementManagement

WO

RW

OR

Security Security

Government and EcosystemGovernment and Ecosystem