3 years of OpenStack with Intel IT Das Kamhout Principal Engineer, - - PowerPoint PPT Presentation

3 years of openstack with intel it
SMART_READER_LITE
LIVE PREVIEW

3 years of OpenStack with Intel IT Das Kamhout Principal Engineer, - - PowerPoint PPT Presentation

3 years of OpenStack with Intel IT Das Kamhout Principal Engineer, Cloud Architect @dkamhout Greg Bunce Automation and Integration Lead Sridhar Mahankali Cloud Architect changing traditional thinking 100,000 Intel Employees 164


slide-1
SLIDE 1

3 years of OpenStack with Intel IT

Das Kamhout – Principal Engineer, Cloud Architect @dkamhout Greg Bunce – Automation and Integration Lead Sridhar Mahankali – Cloud Architect

slide-2
SLIDE 2

6,500 IT Employees

59 IT sites globally

150,000 Connected Systems

40,000 Handheld Devices

100,000 Intel Employees

164 Intel Sites across 63 Countries

68 Data Centers

25% reduction with virtualization

inspire employees IT is business changing traditional thinking service reliability

Intel Confldential

slide-3
SLIDE 3

Intel Data Center Proflle

Intel has flve major groups currently driving individual data center requirements (DOMES):

Design

Design Computing

§ Supports chip design community

D

Office

General Purpose

§ Supports typical IT and customer services

O

Manufacturing

§ Supports fabrication and assembly

M

Enterprise

§ Enterprise applications supporting e Business and

ERP

E

Services

S

§ External facing applications

slide-4
SLIDE 4

Cloud: Experience from our Design Computing Grid

IT Learnings

  • Abstracted the hardware
  • Abstracted the location
  • Service management
  • Service provisioning

1 Source: Intel IT internal analysis. Savings from DCV expected to deliver net present value over 8 years. Intel IT white paper: “Intel IT Data Center Solutions: Strategies to Improve Efficiency” http://communities.intel.com/docs/

DOC-4220

2 Source. Intel IT white paper on projected Intel net present value. “Realizing Data Center Savings with an Accelerated Server Refresh Strategy” http://communities.intel.com/docs/DOC-3489

Data Center Virtualization

Offfioading Design Workloads to Virtual Linux* Clusters

$0M 2006-1H 2006 2007 2008 $33M $25M 0.99M 1.18M 1.85M 2.31M 59% 63% 70% 78%

80% Utilization and an estimated $200M Value

slide-5
SLIDE 5

Hosting Business Goals

Incr Increase Velo locit city, Zero Do Down wntim ime, Grow w wit with h Fla lat Bud udget Velocity ty <1hr for VMs Reduce Incidents ts Scheduled Downtimes the norm Susta tain Operati tions Velocity ty Idea to Production in <1 day Zero Down wnti time me “Always On” for Apps/Services Grow w wi with th Flat t Budget Increase in Engineer:Server and TB Ratio

slide-6
SLIDE 6

Server Landing Process (before Q4 2010)

Customer enters Request in RADAR Reassess Requirements Enter KCDB escalation info Request Backup setup for VM if needed Server Request Fulfilled Assign to Site DC Ops Representative Request Network Addresses (Primary/Backup) Install OS Using Altiris Configure Backup NIC

  • n all VMs

Post Build Verification Enroll VM in ISD Care Patching (Sat 8-2) Install Heartbeat Monitoring for the VM Grant User Permissions Close IPRO Ticket Notify AM Pick-up Approved Dedicated Server Requests Assign Existing or Purchase Server Create IPRO Requests for Dedicated Server Landing IPRO Pick-up VM Requests Check Capacity Validate Capacity in SHERPA Assign LUNs; Create cutsheet for VM Sherpa/CPA Forecast Capacity Mgmt Worksheet Analyze Further and Design Solution Location (Customer, AM, Technologist Involvement) Validate Configuration in SHERPA Create Engagement Agreement (EA) Notify Customer

  • f Server

Availability Address Server Issues Implement EA Decommission Request IPRO RADAR @http:// hosting.intel.com AM Updates Customer of Status Got Capacity? Physical

  • r Virtual?

Solution Possible? Yes No Standard Request? Review all Requests in HUM meeting. Assign server requests (Virtual & Dedicated) to SERVER AM Gather App and Server Requirements at Discovery Meeting with Customer; discuss EA/Costs Yes No Customer Accepts Yes No Related Decommission Yes No Enter forecast in SHERPA/CPS Forecasting Tool Cutsheet Pickup/Create IPRO and/or Cutsheet Landing Request Requestor/ Customer Account Manager (AM) MAS Technologist DIS IHS ADS Procureme nt DC Operations

2009 90 days physical 24 days virtual 2010-11 <3hrs virtual 2 weeks for networks 2012-2013 <30 minutes compute storage and network Next up Idea to Production Service in < 1 day

slide-7
SLIDE 7

Private Cloud Economics

Own the Base

7

Rent the Spike

Performance

Predictability

slide-8
SLIDE 8

Intel IT Cloud Strategic Direction

Deliver the necessary changes in how we expose applications/data to improve end user productivity Drive the transformation to a large-scale automated Hybrid Cloud infrastructure Accelerate the transformation of the Enterprise IT industry to Cloud

slide-9
SLIDE 9

History and Path to Open Cloud

9

slide-10
SLIDE 10

Intel IT Cloud Quick History

Design Grid since 1990’ 1990’s 60k servers across 60+ datacenters Cloud’s Uncle Ente terprise Private te Cloud 2010 2010 13k VMs across 10 datacenters 75% of Enterprise Server Requests 80% virtualized Open Source Private te Cloud 2012 2012 1.5k VMs across 2 datacenters Running cloud-aware and some traditional apps

slide-11
SLIDE 11

Vision: Federated, Interoperable, Open Hybrid Cloud

  • Feder

Federated: ted: IT manages one set of identities,

authorizations, and set of security review

  • processes. Users get seamless integration with

systems and apps.

  • In

Interoperable le: Standard service orchestration

and management, enabling elastic operation and ffiexibility, while minimizing lock-in.

  • Op

Open: n: Includes open source and open

  • standards. Common APIs and abstraction layers

to rapidly consume cloud services among providers.

11

App compone nents will will run run acr cross pub ublic lic and nd priv rivate clo cloud uds

Public Cloud Service Provider Public Cloud Service Provider Enterprise Private Cloud

IaaS, P IaaS, PaaS, and/or aaS, and/or Saas Saas

slide-12
SLIDE 12

Enterprise Adoption Roadmap - Path to Open Cloud Ecosystem

Year 1 Year 2 Year 3 Year 4 Year 5 End End User User Ap App Dev Dev Ap App Own wner IT Ops IT Ops Federated, Interoperable, and Open Cloud 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 Consume mers Legacy Applications on dedicated Infrastructure Start

slide-13
SLIDE 13

Intel IT Pre-OpenStack – Private Cloud Gen 1

Year 1 Year 2 End End User User Ap App Dev Dev Ap App Own wner IT Ops IT Ops Enterprise Legacy Apps Compute, Storage, and Network Simple Compute IaaS Enterprise Legacy Apps Cloud Aware Apps Complex Compute IaaS Simple Compute IaaS Compute, Storage, and Network Consume mers Legacy Applications on dedicated Infrastructure Start

  • Provides Self-Service to App Teams
  • Connect to ALL available infrastructure
  • $14M savings through resource pooling
  • Internal Code for logic/gui

But…

  • Cloud-aware app teams needed more
  • Too much technical debt to create full

IaaS

slide-14
SLIDE 14

Intel IT Post-OpenStack Private Cloud Gen2

Year 1 Year 2 Year 3 End End User User Ap App Dev Dev Ap App Own wner IT Ops IT Ops Enterprise Legacy Apps Compute, Storage, and Network Simple Compute IaaS Enterprise Legacy Apps Cloud Aware Apps Complex Compute IaaS Simple Compute IaaS Compute, Storage, and Network Full Private IaaS Cloud Aware Apps Legacy Apps Private PaaS Consume mers Legacy Applications on dedicated Infrastructure Start

  • 2011 investigated all open

and proprietary solutions

  • Analysis led to decision:

OpenStack for Private IaaS

  • June 2012 online for

production cloud-aware apps But…

  • Need a public cloud solution
  • Legacy apps need love too
slide-15
SLIDE 15

Intel IT OpenStack – Hybrid Cloud and the future

Year 3 Year 4 Year 5 End End User User Ap App Dev Dev Ap App Own wner IT Ops IT Ops Federated, Interoperable, and Open Cloud Open Cloud Full Private IaaS Hybrid IaaS Cloud Aware Apps Legacy Apps Private PaaS Private PaaS Cloud Aware Apps Legacy Apps Consume mers Legacy Applications on dedicated Infrastructure Start

  • Live Migration Enabled
  • Single Control Plane
  • 2 POCs for Hybrid

OpenStack in progress Very close to our year 5 goal

slide-16
SLIDE 16

Our Choices and Architectural Implementation

16

slide-17
SLIDE 17

Key Concepts

  • Abstract users from underlying Cloud providers while exposing key HW

features

  • Support multiple cloud providers, both private and public
  • Common identity and entitlement services for reuse across interfaces
  • Open Source first, minimize proprietary API lock-in
  • Minimize internal technical debt, be part of the community to scale
  • Stay pragmatic, as we expand – not always 100% greenfield
  • Support cloud-aware and traditional apps
slide-18
SLIDE 18

Technical Strategy (AS IS)

IaaS Public Clouds Internal Network Exclave App Owner/ Developer PaaS & DBaaS IaaS

  • Started in 2010
  • Use our own capacity before paying an external

provider

  • Intel IT at Service Provider size
  • Use public cloud for speciflc purpose (SaaS, some IaaS)

PaaS & DBaaS On Premise Firewa wall

slide-19
SLIDE 19

Technical Strategy (TO BE)

Public Clouds Internal Network Exclave IaaS Smart orchestration layer

  • Move apps/data among clouds via policies
  • Deliver security, capacity and cost optimization

Orchestr trati tion Burst Firewa wall On Premise App Owner/ Developer PaaS & DBaaS

slide-20
SLIDE 20

20

Why Intel IT Selected OpenStack for its IaaS Control Plane

  • Velocity:

− Yields direct control over the capabilities that business demands and is forward- leaning in terms of application / service development, delivery, and operations − Geared toward Agile Methodologies, DevOps, and Continuous Integration / Continuous Delivery (CI/CD) & Deployment

  • Capability:

− OpenStack automation platform which is deflned by its APIs − Provide granular on-demand services which seed innovation by satisfying simple- to-complex use cases to deliver at the pace business demands

  • Efflciency & Quality:

− We leverage the same tool-chain used by the OpenStack community for developing, building, validating, and deploying our data center operating system

slide-21
SLIDE 21

API Open Stack Control Plane Open Source HW/SW Stack (KVM, Ceph) Nova Cinder Swift Heat Neutron GUI CLI Managed Infrastructure

Keystone Auth

Phase 2014

1. Open Stack Control Plane manages Mixed Infrastructure 2. Absorbing all existing VM Lifecycle management Self-Serve and Admin UI Ceilometer Active Directory Service Management Hypervisor A Existing Infrastructure

SDN SN/NAS

10 Internal Data Centers 2 External Data Centers All VMs controlled by OpenStack

slide-22
SLIDE 22

Areas to Close for Enterprise

Keep VMs up for traditional/legacy apps:

  • 1. Shared Block Storage – for boot volumes, and data
  • 2. Live Migration for maintenance of hosts – working in some implementations
  • 3. Restart of instances when host fails
  • 4. Disaster Recovery
  • 5. Connect to Infrastructure where this already works

Enable a federated Hybrid cloud environment:

  • 1. End users interface allowing for seamless use across zones, regions, and across clouds
  • 2. Identity federated across instances and clouds
  • 3. Orchestration across global/multiple instances

Highly Available Infrastructure Services (cloud built as cloud) Rolling Upgrades – initial improvements in Icehouse Secure, Auditable – Role Based Access, Regulatory Compliance, Audit Trails

slide-23
SLIDE 23

Items for 2013 Completion

Comp mpute te

  • 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 ☐

St Storage

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

Netw tworking

  • Self-Service Network Services þ
  • SDN Network Integration þ
  • Load Balancer as a Service ☐ (temp internal only solution in place)

Sup upport rt Enterp rpris rise and nd Clo loud ud Awa ware Worklo rkloads Trans nsform rming ing entir ire Da Datace center r to Soft ftwa ware Exposed

slide-24
SLIDE 24

2014 Focus Areas

  • Rolling Upgrades – no tenant downtime for resources or services
  • Connection into ALL existing infrastructure – Single Control Plane
  • Disaster Recovery between sites for VM tenants
  • Restart of VM when host fails
  • Hybrid Cloud enabled through Horizon
  • Use OpenStack to do traditional work – Backup and Recovery, Bare Metal

Provisioning, LB, FW, and more

  • Use OpenStack to replace internal code – DBaaS, LBaaS

24

slide-25
SLIDE 25

People

25

slide-26
SLIDE 26

Simplify – Integrate and Collaborate

26

66%

Specialists/Silo’s

HW Centric 38 Roles SW Centric 13 Roles

Dev Ops

Operati tions Developme ment t Automa mati tion

Creativity

Procedure Software Physical Infrastructure

slide-27
SLIDE 27

Major Workforce Shifts

  • Training

− IT Sysadmins retrained for CLI and Scripting fundamentals − All developers put into the ops flre… take tickets, root cause, and learn hands on − Key technologies taught broadly; OpenStack*, Linux*, Python*

  • Scope

− From Technical Depth to Technical Breadth

− Sysadmins understand and can solve issues in compute, storage, network and tenant

  • perations/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 cha chang nges to skills kills and nd metho hods

slide-28
SLIDE 28

Change or become Irrelevant

28

slide-29
SLIDE 29

Intel IT Open Cloud: Result

Agility Automation Efflciency

29

slide-30
SLIDE 30

Are you involved?

  • Join us on Wednesday at 2pm in Room B407 For the Enterprise

BoF Kick-Off

  • Hear more from Intel IT at 5:20pm on Wednesday in B312
  • Help us create blueprints – Go Community!!!!
slide-31
SLIDE 31

Wrap Up - Summary

  • Our Direction = Federated, Interoperable and Open Cloud

− Strong success with our Enterprise Private Cloud (Gen1) − Open Cloud (Gen2) in production − Connecting our existing infrastructure to single control plane (OpenStack) − Lots of space and opportunity for us all to contribute

  • Changes required to run cloud at scale

− Culture − Skills − Business processes − Technology

slide-32
SLIDE 32

32