1

Intel IT Open Cloud – What’s Under the Hood, and How Do We Drive It? Das Kamhout, Intel IT, Principal Engineer, Intel Corporation

CLDS004

2

Agenda

• ODCA Cloud Maturity Model • Current Intel IT Cloud Data • Business Goals and Architecture • Under the Hood of the Open Cloud • How We Use the Open Cloud • Workforce Changes • Summary

3

ODCA Cloud Maturity Model Update

4

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 optimized

5

Enterprise Adoption Roadmap

Year 1 Year 2 Year 3 Year 4 Year 5

End User

App Dev

App Owner

IT Ops

Federated, Inter-

operable, 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 Le

gacy

App

licat

ions

on

dedi

cate

d In

fras

truc

ture

Sta

rt

6

Current IT Cloud Data

7

2014+ 2012

IT’s Cloud Transformation 2010 2000-2009

Design

Office/Enterprise

Traditional Hosting

Mainstream Virtualization

Intel Cloud 1.0 Hybrid Cloud 2.0 Converged Cloud

12% Virtualized 42% Virtualized 75% Virtualized 75%+ Virtualized 90+ Day

Provisioning 10 day

Provisioning On Demand

Compute

On Demand Compute, Network, Storage

Silos of Capacity

Pooled Capacity Segmented Clouds Converged Clouds, burst capacity @ 3rd

Party Manual Ticketed Service Request

Manual Ticketed Service Request

Some on demand Request fulfillment

Full Self Service Request fulfillment

Varying Server Reliability

99.7% VM Reliability

99.7-99.9% Availability

99.99% Availability Capable

Public Physical Hosting

Office Cloud

Public

Office/Enterprise /Services

Office/Enterprise /Services

8

Open Cloud Business Goals, Architecture

9

Business Goals

Increase Velocity, Zero Downtime, Grow with Flat Budget

Velocity <1hr for VMs

Reduce Incidents Scheduled Downtimes the

norm

Sustain Operations

Velocity Idea to Production in <1 day

Zero Downtime “Always On”

for Apps/Services

Grow with Flat Budget Increase in Engineer:Server

and TB Ratio

10

Top Challenges

Business Uptime • Always On at optimal cost Security • Securing end user data and data interconnects • Minimizing impact of attacks (DDOS) • Detection immediately and quarantine Unit Cost • Challenged to <10cents per CPU hour and dropping fast • IT Hosting Team must operate like a Cloud service provider Workforce Transformation • From proprietary integrated solutions to open solutions • Transition to highly automated

Intel IT Cloud Future

Intel® Atom™ Intel® Xeon® Intel® Xeon® Phi™

Storage Compute Network

Physical Infrastructure

Infrastructure Services

App Platform Services Analytics Messaging Data Web

App Services Location Context Recommendation Identity

End User

Applications

Reusable Services empowering our end users

12

Capacity and Performance

Delivery – OS and Software

Configuration

Event

Dynam

ic Managem

ent of End-to-End Services

Dat

a Ia

aS

Servers Servers Servers

Host OS Host OS Host OS

Scale Out Data Services for Application Data Block and Object

Host Servers Host Servers Host Servers

Hypervisor A Hypervisor B

Guest Guest Guest Guest Host OS

Com

pute

Iaa

S Compute Containers for Application Workloads

Servers Servers

Host Servers

Hypervisor A

Guest Host OS Host OS

Dat

abas

e as

a

Ser

vice

Resilient Name Services and Load Balancers

Scale Out Data Base Services Memcached, MySQL*, MongoDB* and Cassandra*

13

Under the Hood of the Open Cloud

14

6 Months

Infr

astr

uctu

re

As

a Ser

vice

Compute Storage Network

12-18 Months

Phys

ical

In

fras

truc

ture

IaaS

Compute (Nova*)

Block Storage (Cinder*)

Object Storage (Swift*)

Network (Neutron*)

Dashboard (Horizon*)

OS Images (Glance*)

Open-Source (OpenStack*)

Manageability

3 Months

Mon

itoring

As

a Ser

vice

Watcher (Nagios*, Shinken*,

Heat*)

Decider (Heat)

Collector (Hadoop*)

Actor (Puppet*, Cfengine*)

Open-Source Foundation

Inte

rfac

es

GUI (Graphical User Interface)

API (Application Programming Interface)

6 Months

Release Cadence

App

Pla

tfor

m

Ser

vice

s PaaS

Analytics Messaging Data Web

3 Months

15

Persistent Storage Architecture

swift post my_container my_files cinder create --Vol1 Vol1 1024

Object Storage Block Storage

Ceph* RADOS Gateway

Storage Nodes Storage Nodes Storage Nodes Storage Nodes

Storage Nodes Storage Nodes Storage Nodes Storage Nodes

10Gbps

IP Network

OpenStack Node

OpenStack Node

OpenStack Node

OpenStack Node

OpenStack Node

10Gbps Ceph RADOS Gateway

Block: Direct access to storage nodes

Object: Access to storage nodes through Gateway

16

Network Design

Physical Network L3 Switch L3 Switch

L3 Switch L3 Switch Load Balancer

Load Balancer

Compute Node

Virtual Switch

VM VM

VM VM

VM VM

Compute Node

Virtual Switch

VM VM

VM VM

VM VM

Compute Node

Virtual Switch

VM VM

VM VM

VM VM

Overlay Network SDN Controller

SDN Controller

SDN Controller

OpenStack Controller

OpenStack Controller

OpenStack Controller

VM VM VM Tenant A Tenant B Tenant C

17

Items in flight for 2013 Completion • Compute

• Always on VMs • Boot From Volume (Block) • Live Migration • Restart on Failure

• API Endpoint Encryption (SSL for all API communication) • Highly Available 99.999% APIs

• Storage • Object Storage Proxy Highly Available • Harden open distributed block storage solution

• Networking • Self-Service Network Services • SDN Network Integration • OpenStack Networking • Load Balancer as a Service

Support Enterprise and Cloud Aware Workloads Transforming entire Datacenter to Software Exposed

18

How We Use the Open Cloud

19

Self-Service Cloud Hosting Options

PaaS = Platform as a Service •On demand build and hosting for custom applications •Pre-provisioned, multi-tenant, common platform •Abstracted hardware & software infrastructure supported by IT

IaaS = Infrastructure as a Service •For commercial off-the-shelf software •For custom apps needing control over the entire application stack •You support your entire stack or used managed hosting

Cloud Broker •Contact us when you need help deciding the correct hosting model

Focused Solutions for our End Users

20

Architectural Guidance Item What needs to be done Design for failure Be highly available - assume and actively

test for failure

Stateless Compute Internal state will not be preserved

Scale out (not up) Scaling up always has a break point, scaling horizontal close to “infinite”

Event driven Read requests from a queue instead of synchronous calls

Web Services Utilize web services model to publish/consume; RESTful is preferred

Security Build security into your app - Encrypt everywhere

Prefer Eventual Consistency

Shard data globally; Understand conflicts, understand and use Paxos

DevOps Use automation/remediation for production, deploy continuously

21

Cloud Application Design Patterns

Mobile Active/Passive Active/Active

22

Design Pattern 1: Mobile

• All apps should run on any device

• App backend is hosted in the cloud

• Devices access the app through a browser

• And/or there is a client-side app that interacts with the backend through web services

• All apps should expose web services

Mobile Device

PaaS or IaaS

Application Stack

HTML5 web interface

Mobile App Backend

REST API

Browser URL Native Client Mobile App

Other Apps

23

Design Pattern 2: Active/Passive

• App might not require any changes from traditional

• App deployed to 2 clouds

• Databases are mirrored

• App URL added to GLB – script does health check to either send to active or fail over to the passive instance

• Users connect to an app instance in only one cloud

Application Stack

App 1 instance 1

Cloud #2 Passive

App 1 instance 2

Application Stack

App 1 instance 1

Cloud #1 Active

App 1 instance 2

Load Balancer

Database

End User Clients Global Load Balancer

Database

Mirror

Load Balancer

Active Passive

24

Design Pattern 3: Active/Active

• App deployed to two regions

• Eventual consistency and conflict resolution is built into the developer application

• Database replication is configured

• App URL is added to the GLB for transaction distribution

• Users connect to any app instance in either region – runs simultaneously

Application Stack

App 1 instance 1

Cloud AZ #2

App 1 instance 2

Application Stack

App 1 instance 1

Cloud AZ #1

App 1 instance 2

Load Balancer

Database

End User Clients Global Load Balancer (GLB)

Database

Eventual consistency Conflict resolution provided by App

Load Balancer

25

Cloud-Aware Code-a-thons • Hands-on training event

Code cloud-aware apps and land them in Intel’s private cloud Developers compete against each other for prizes

One day session format: • Presentation from Cloud Team on cloud-aware

• Cloud experts provide roaming “road side assistance”

• Apps graded on how cool, useful and cloud-aware

Sample Apps Created Conference Room Waitlist Find a Parking Spot Enterprise Fund Starter IT Issue Logging with Pictures Café Fruit Status (Banana Finder)

Idea to Service in less than a Day

26

Workforce Changes

27

Major Workforce Shifts

• Training – IT Sysadmins familiar with GUI only (next, next, finish)

retrained for CLI and Scripting fundamentals – All developers put into the ops fire… take tickets, root cause,

and learn hands on – Key technologies taught broadly; OpenStack, Linux, Python

• Scope – Single Tech Depth to Broad Tech Breadth Sysadmins understand and can solve issues in compute, storage,

network and tenant operations/tasks – DevOps as the working model – Small team of experts – Automate everything vs. Knowledge Base articles

• IT shifts away from being the STOP sign bearers Broad changes to skills and methods

DevOps “Support what you build”

• Developers own support and management of their apps

• Using highly automated, agile infrastructure

Operations Development

Automation

Cre

ativ

ity

Procedure

Software Physical Infrastructure

Automation includes: • App Management • Config Management • Release Management • Break/Fix

Integration of duties between development and operations

29

Who Supports What?

Physical Hardware – Compute, Storage, Network

IaaS – Software, Automation

PaaS – Software, Automation

Applications

Datab

ase/

Data S

tore

Developers & App Owners support their app software

and their data

Cloud engineers and developers

support software infrastructure (IaaS, PaaS, Database)

Operations supports the physical hardware

Cloud demands New Support Models

30

Summary

31

Wrap Up - Summary

• Our Direction = Federated, Interoperable and Open Cloud – Strong success with our Enterprise Private Cloud (Gen1) – Open Cloud (Gen2) in production – Lots of space and opportunity for us all to contribute

• Changes required to Transform IT towards cloud –People –Technology –Application Design patterns

32

Call to Action

Do you want to own your destiny for Cloud? • Contribute, share your ideas and code • Create blueprints, help set and create the Open

Cloud direction

Get involved in the Open Data Center Alliance and OpenStack*

33

Additional Sources of Information

PDF of this presentation is available is available from our Technical Session Catalog: www.intel.com/idfsessionsSF. The URL is on top of Session Agenda Pages in Pocket Guide.

34

Session ID Title Day Time Room

CLDS001 Rack Scale Architecture for the Cloud Wed. 1:00 p.m. 2001

CLDS002 Software Defined Data Center (SDDC) Best Known Methods Wed. 2:15 p.m. 2001

CLDS003 Intel® Microservers – Density, Power, and other Design Considerations for the Next Generations of Intel® Server SoCs Wed. 3:45

p.m. 2001

CLDS004 Intel IT Open Cloud – What’s Under the Hood, and How Do We Drive It? Wed. 5:00

p.m. 2001

CLDS005 How Intel® Technology Can Unlock Flexible Tiered Storage Solutions in the Cloud Wed. 2:15

p.m. 2005

CLDS006 Extending Open Networking Platform (ONP) for the Next Generation Server Architectures Wed. 3:45

p.m. 2005

CLDS007 OpenStack* Swift Erasure Code: A Smart Cloud Storage Solution with Higher Performance and Lower TCO Wed. 5:00

p.m. 2005

CLDS008 Enabling Data Center Optimization through the use of New Hardware Telemetry on the Intel Haswell Microarchitecture Thur. 10:45

a.m. 2001

CLDS009 Server Platforms and Persistent Memory: The Impact of a New Tier Between Memory and Storage Thur. 1:00

p.m. 2001

CLDS010 MXC for Silicon Photonics – The Next Generation Optical Connector Thur. 2:15

p.m. 2001

= DONE

Other Technical Sessions

35

Legal Disclaimer INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. A "Mission Critical Application" is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death. SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS. Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined". Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information. The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or go to: http://www.intel.com/design/literature.htm Intel, Look Inside and the Intel logo are trademarks of Intel Corporation in the United States and other countries.

*Other names and brands may be claimed as the property of others. Copyright ©2013 Intel Corporation.

36

Risk Factors The above statements and any others in this document that refer to plans and expectations for the third quarter, the year and the future are forward-looking statements that involve a number of risks and uncertainties. Words such as “anticipates,” “expects,” “intends,” “plans,” “believes,” “seeks,” “estimates,” “may,” “will,” “should” and their variations identify forward-looking statements. Statements that refer to or are based on projections, uncertain events or assumptions also identify forward-looking statements. Many factors could affect Intel’s actual results, and variances from Intel’s current expectations regarding such factors could cause actual results to differ materially from those expressed in these forward-looking statements. Intel presently considers the following to be the important factors that could cause actual results to differ materially from the company’s expectations. Demand could be different from Intel's expectations due to factors including changes in business and economic conditions; customer acceptance of Intel’s and competitors’ products; supply constraints and other disruptions affecting customers; changes in customer order patterns including order cancellations; and changes in the level of inventory at customers. Uncertainty in global economic and financial conditions poses a risk that consumers and businesses may defer purchases in response to negative financial events, which could negatively affect product demand and other related matters. Intel operates in intensely competitive industries that are characterized by a high percentage of costs that are fixed or difficult to reduce in the short term and product demand that is highly variable and difficult to forecast. Revenue and the gross margin percentage are affected by the timing of Intel product introductions and the demand for and market acceptance of Intel's products; actions taken by Intel's competitors, including product offerings and introductions, marketing programs and pricing pressures and Intel’s response to such actions; and Intel’s ability to respond quickly to technological developments and to incorporate new features into its products. The gross margin percentage could vary significantly from expectations based on capacity utilization; variations in inventory valuation, including variations related to the timing of qualifying products for sale; changes in revenue levels; segment product mix; the timing and execution of the manufacturing ramp and associated costs; start-up costs; excess or obsolete inventory; changes in unit costs; defects or disruptions in the supply of materials or resources; product manufacturing quality/yields; and impairments of long-lived assets, including manufacturing, assembly/test and intangible assets. Intel's results could be affected by adverse economic, social, political and physical/infrastructure conditions in countries where Intel, its customers or its suppliers operate, including military conflict and other security risks, natural disasters, infrastructure disruptions, health concerns and fluctuations in currency exchange rates. Expenses, particularly certain marketing and compensation expenses, as well as restructuring and asset impairment charges, vary depending on the level of demand for Intel's products and the level of revenue and profits. Intel’s results could be affected by the timing of closing of acquisitions and divestitures. Intel's results could be affected by adverse effects associated with product defects and errata (deviations from published specifications), and by litigation or regulatory matters involving intellectual property, stockholder, consumer, antitrust, disclosure and other issues, such as the litigation and regulatory matters described in Intel's SEC reports. An unfavorable ruling could include monetary damages or an injunction prohibiting Intel from manufacturing or selling one or more products, precluding particular business practices, impacting Intel’s ability to design its products, or requiring other remedies such as compulsory licensing of intellectual property. A detailed discussion of these and other factors that could affect Intel’s results is included in Intel’s SEC filings, including the company’s most recent reports on Form 10-Q, Form 10-K and earnings release.

Rev. 7/17/13