odca usage model overview and outlook april 2014
DESCRIPTION
This presentation covers the purpose and structure of the ODCA work groups before diving deeper into the architectural framework and service tiers developed by the ODCA. We will discuss the work and publications completed by our members to accelerate cloud adoption. The final piece of the presentation will be to provide insight into current and future projects on the technical coordination committees road-map. You can view the full recorded webinar of this content here: https://www.brighttalk.com/webcast/9831/109843TRANSCRIPT
THE OPEN DATA CENTER ALLIANCE: ODCA UM OVERVIEW
Catherine Spence, Chair, Technical Coordination Committee, IT Principal Engineer, IntelIan Lamont, Chair, Security Workgroup, IT Security Specialist, BMWRyan Skipp, Co-Chair, Business Transformation Workgroup, Portfolio & Solution Development, DTAG/T-Systems
AGENDA
• Open Data Center Alliance* (ODCA)• Architectural Framework• Usage Models• Proposal Engine Assistant Tool (PEAT) Tool• 2014 Topics• Summary
2
Drive new levels of IT agility through delivery of unified customer requirements for cloud computing enabling secure federation of cloud services, automation of IT infrastructure, common management and policy for data center resources, and transparency in cloud service capability and metrics.
Create & Deliver Unified Customer Requirements
Through Defining Usage Models
CollaborateWith Standards Orgs and
Industry to Accelerate Deployment and map applicable
standards
CommitRoadmaps, Checklists and RFP
Questions to Guide Internal IT Deployments
3
Alliance Leadership and Workgroup Structure
InfrastructureWork Group
Manageability and Services Work Group
Regulation and EcosystemWork Group
SecurityWork Group
DataWork Group
China Technical Sub-Group
Steering Committee Board of Directors
Intel:Technical Advisor
Technical Coordination Committee
External Technical Forums
Standards Organizations
Contributor Members
Solution Provider Members
AdopterMembers
Liaisons
Active WG participation
4
Invited WG Participation on UMs and projects
Review & input roadmap & collateral
Business Transformation
Work Group
WORK GROUP LEADERSHIP
Work Group Chair
InfrastructureEd Simmons, UBS Dave Casper, Moogsoft
Manageability & Services
Iain Macrae, NABPrasanna Sridhar, Infosys
Security Ian Lamont, BMWData Services Shawn Ramsey, DisneyRegulation Pankaj Fichadia, NABBusiness Transformation
Ryan Skipp, T-SystemsPankaj Fichadia, NAB
TCC Catherine Spence, Intel IT
5
DRIVING CLOUD ADOPTION
Successstories
Awareness
Colla
bora
tion
ODCA Defines Requirements
Providers Deliver
Solutions
Enterprises Adopt
Solutions
ODCA Drives Scale with Results Sharing
New/Enhanced Requirements Defined
Best Practices Fuel Broad Deployments
Lead Enterprises Invest in Required
Solutions
Providers Invest to Meet Demands
6
ODCA Driving Positive Results
7
Delivering cloud and big data services based on ODCA
requirements
Strategy and procurement decisions anchored on ODCA
requirements.Building cloud based on ODCA requirements
Leveraging ODCA as a pragmatic guild for internal & client cloud-implementations
UMs used for current clouds & future planning
of new cloud services
Driving RFPs based on ODCA requirements
Broad scale integration of UMs into public, private and hybrid
cloud offerings
Leveraging ODCA for full scale private cloud build out, big
data and networking strategy
Broad integration of ODCA UMs to global cloud strategy
and procurements
AGENDA
• Open Data Center Alliance* (ODCA)• Architectural Framework• Usage Models• Proposal Engine Assistant Tool (PEAT) Tool• 2014 Topics• Summary
8
ALLIANCE CLOUD MATURITY MODEL SUMMARY
Level Description Enterprise Cloud Maturity
CMM 0 None Legacy Applications on dedicated Infrastructure
CMM 1 Initial, ad-hoc Analysis of Current Environments’ Cloud Readiness
CMM 2 Repeatable, opportunistic Processes for Cloud Adoption Defined
CMM 3 Defined, systematic
Tooling and Integration exists for Automated Cloud Usage
CMM 4 Managed & measurable
Cloud Aware Applications, deployed according to Business requirements on Public, Private and
Hybrid platforms – Manual Federation
CMM 5 Optimized Federated, Interoperable, and Open Cloud
Use of cloud becomes more sophisticated, comprehensive and optimized9
ENTERPRISE ADOPTION ROADMAP
Year 1 Year 2 Year 3 Year 4 Year 5
End User
App Dev
App Owner
IT Ops
Federated, Interoperable,
and Open Cloud
Simple SaaS
Enterprise Legacy Apps
Compute, Storage, and
Network
Simple Compute IaaS
Simple SaaS
Enterprise Legacy Apps
Cloud Aware Apps
Complex Compute IaaS
Simple Compute IaaS
Compute, Storage, and
Network
Complex SaaS Hybrid SaaS
Full Private IaaS Hybrid IaaS
Cloud Aware Apps
Legacy Apps
Private PaaS Hybrid PaaS
Cloud Aware Apps
Legacy Apps
Consumers
10
Legacy
Applic
ati
ons
on
dedic
ate
d Infr
ast
ruct
ure
Sta
rt
CONCEPTUAL ARCHITECTURE HYBRID CLOUD
11
SERVICE TIERS
12
AGENDA
• Open Data Center Alliance* (ODCA)• Architectural Framework• Usage Models• Proposal Engine Assistant Tool (PEAT) Tool• 2014 Topics• Summary
13
Finer Grain Usage Models
Master Usage Models
USAGE MODEL OVERVIEW
• Virtual Machine Interoperability• Long Distance Migration• IO Control• Service Catalog• Standard Units of Measure • Provider Assurance• Security Monitoring• Regulatory Framework• Security Data Framework• Data Security• Data Management
• Carbon Footprint• SaaS Interoperability• PaaS Interoperability• Interoperability across Clouds• Identity Management Interoperability• Cloud Based Identity Provisioning• Cloud Based Identity Governance and Auditing• Single Sign on Authentication• IaaS Privileged User Access• SW Entitlement Management Framework
Usage Model
Contents:
• Exec Summary
• Problem Statement
• Use Cases
• RFP Questions
• Industry Action
Compute IaaS 1.0, Scale-out Storage 1.0, Software-Defined Networking 1.0
Service Orchestration 1.0
Commercial Framework 1.0
Information as a Service1.0
Infrastructure as a Service
15
COMPUTE IAAS USAGE SCENARIOS
16
SCALE-OUT STORAGE
Appears “infinite” for capacity and performance17
Defines on-demand storage capacity at service-level agreement performance
SOFTWARE DEFINED NETWORKING
Allows rapid server and bandwidth growth, increasing geographic concentration, elasticity, and mobility 18
EXAMPLE IAAS REQUIREMENTS• Service is open and is standards-based. Describe how the service meets this principle and
any limitations towards the ODCA principle. • The service must support a wide range of x86-based operating systems, including Windows*
(server and desktop OS), Solaris* x64 and Linux* (leading distributions) in 32-bit and 64-bit versions
• The service must support network isolation controls for inbound and outbound traffic• The service must support the deployment of Web, Application, Database and Infrastructure
Service components, such as LDAP components • The service must support alignment with Information Technology Infrastructure Library (ITIL)
processes for change, incident and configuration management• The service provider must provide options for consumer network connectivity, such as
internet VPN, and leased lines. In addition, the service provider must articulate any other network requirements, stipulations and constraints, such as NAT, IP address overlays, and latency controls.
19
SERVICE ORCHESTRATION
Enable standardized automation that scales cloud services with consumer demand
20
EXAMPLE SERVICE ORCHESTRATION REQUIREMENTS Service lifecycle phases are fully documented and available online, with defined sub-steps,
actions, and success/failure conditions. The documentation must include the Automated Service Provisioning Process, from beginning to end, and indicate any manual steps involved.
A downtime and maintenance schedule is available on-demand, indicating which functions and service elements are maintained online and which require downtime.
Describe your handling of potential availability issues such as significant cloud computing outage, high network load, or insufficient bandwidth access.
Committed service request completion times are provided for cloud service requests as follows: (1) new VM provisioning, (2) add, move, or change and (3) service termination and deletion.
21
INFORMATION AS A SERVICE
Getting the right information, in the right format at the right time 22
INFORMATION ARCHITECTURE
23
EXAMPLE INFORMATION AS A SERVICE REQUIREMENTS• Provide a common semantic view of the data regardless of the source or number of sources
from which the data originated
• Provide the ability for users of the system to define tags (text strings); to tag data, information,
reports, pages, and other constructs; and retrieve these elements through their association to
one or more tags
• Support mobile access to data and information contained within the Information as a Service
ecosystem, as well as expose management functionality through a mobile application or
mobile web access
• Provide search, reporting, business intelligence, and analytics capabilities for deriving meaning
from and presenting the underlying data and information stored within the Information as a
Service ecosystem
• Provides a web portal to which information, reports, analytics, and other result sets can be
published24
COMMERCIAL FRAMEWORK
25
MASTER SERVICES AGREEMENT DRIVERS
26
AGENDA
• Open Data Center Alliance* (ODCA)• Architectural Framework• Usage Models• Proposal Engine Assistant Tool (PEAT) Tool• 2014 Topics• Summary
27
PROPOSAL ENGINE ASSISTANT TOOL (PEAT)
Online tool to generate RFP Requirements from the usage models
In three easy steps!
28
1 2 3
PEAT EMAIL
29
AGENDA
• Open Data Center Alliance* (ODCA)• Architectural Framework• Usage Models• Proposal Engine Assistant Tool (PEAT) Tool• 2014 Topics• Summary
30
2014 TOPICS: TCC ROADMAP
DriveAdoption
Speeding cloud adoption and influencing solution capabilities/consistency
Enrich UMs &Content
Q1’14 Q2’14 Q3’14 Q4’14 Q1’15
June Nov
SUoM POC
IaaS Meta framework MUM
Service Catalog
Scale out Storage
Meta Framework POC
VM Interop POC
Common Compute Unit POC
Procurement/Auth
CMMForensics/ eDiscovery
Data Exchange
Cloud-Aware Apps BP
Cloud Adoption
Metadata/Tagging
Purchasing Guidelines
Cloud Broker BP
Cloud Broker
Identity POC
Cloud Strategy Transition
Transform
Provider Assurance
Service Orch POC
SDN
Risk
Cloud Benefits BP
March 2014 Update
AGENDA
• Open Data Center Alliance* (ODCA)• Architectural Framework• Usage Models• Proposal Engine Assistant Tool (PEAT) Tool• Applying ODCA Principles• Summary
32
SUMMARY
• Accelerating ODCA members and industry path to cloud computing• Use usage models and PEAT tool now• Learn about the ODCA work and join in
33
THANK YOU
34
Intel Serves as Technical Advisor to the Alliance
HUNDREDS OF GLOBAL IT LEADERS
35
Industry Collaborations: Critical to Alliance Mission
Aligning standards development with customer requirements and speeding industry standards solutions to market
36