From iron to the cloud and beyond

Presentation for SFSU Stefano Maffulli, OpenStack Community Manager 2012-05-17 What do these things have in common?

Who am I

The lesson of Brunelleschi

 Be able to study how things work  Study the source code  Be able to modify and adapt what you learn  Modify the code  Be able to teach others  Copy the code and share it with others What is Web based applications Virtualization

Cloud computing

Services on demand IT on demand Evolution of IT

Mainframe Enterprise Cloud Computing Computing Computing

1960 1980 2000 2020

Disruptions Evolution of computing models

SLA 99.999 99.9 Always on

Scaling Vertical Horizontal

Hardware Custom Enterprise Commodity

HA type Hardware Software

Software Centralized Decentralized Distributed

Consumption Centralized Shared Self-service

Mainframe Enterprise Cloud Computing Computing Computing

1960 1980 2000 2020 The legacy enterprise computing The web scale The real paradigm shift

“... get into the [] mindset ... robustness has to be designed into your software ... assume that the hardware [is] … unreliable and broken ... at any point.” -- Adrian Cockcroft, Netflix Chief Cloud Architect The details The stack

Software As A Service

Platform As A Service

Infrastructure As A Service The trade-offs Enter OpenStack Virtualized data centers, servers come first

HYPERVISORS PROVIDE ABSTRACTION BETWEEN APPS AND HARDWARE (SERVERS) HOST 1 HOST 2 HOST 3 HOST 4, ETC.

VMs

Hypervisor: Turns 1 server into many “virtual machines” (instances or VMs) (VMWare ESX, Citrix XEN Server, KVM, Etc.)

Hardware abstraction for Better resource utilization each server for each server

1. Virtualization 2. Cloud Data Center 3. Cloud Federation Automation & Efficiency Next come storage, networks

ABSTRACTION BETWEEN APPS AND HARDWARE

Compute Pool Network Pool Storage Pool Virtualized Servers Virtualized Networks Virtualized Storage

Flexibility, Efficiency are Resource pools for apps key drivers starting to form...

1. Virtualization 2. Cloud Data Center 3. Cloud Federation Automation & Efficiency Questions arise when virtual environments grow

“VM SPRAWL” CAN MAKE THINGS UNMANAGEABLE VERY QUICKLY

APPS USERS ADMINS

How do you make your apps How do you empower cloud aware? employees to self-service? Where should you provision How do you keep track of it new VMs? all?

+

1. Virtualization 2. Cloud Data Center 3. Cloud Federation Automation & Efficiency VM sprawl can make things unmanageable quickly

APPS USERS ADMINS

A Cloud Management Layer Is Missing

+

1. Virtualization 2. Cloud Data Center 3. Cloud Federation Automation & Efficiency A management layer to add automation and control

APPS Connects to apps via APIs USERS ADMINS

Self-service Portals for users CLOUD OPERATING SYSTEM

Creates Pools of Resources Automates The Network

1. Virtualization 2. Cloud Data Center 3. Cloud Federation Automation & Efficiency What's next Enterprise Private Clouds run cloud operations Public Clouds run systems… cloud operating systems… But you can’t interoperate if public clouds are built on proprietary software

1. Server Virtualization 2. Cloud Data Center 3. Cloud Federation Automation & Efficiency Imagine having a Common Platform across clouds

Seamlessly transporting workloads

1. Virtualization 2. Cloud Data Center 3. Cloud Federation Automation & Efficiency Connecting clouds to create global resource pools

Common software platform making Washington federation possible Public Cloud

Texas California Europe Private Cloud Private Cloud Public Cloud

Mirror content to a Cloudburst into Run applications on a private cloud in a multiple public private cloud in your own colo facility for clouds around the data center. disaster recovery world when demand surges

1. Virtualization 2. Cloud Data Center 3. Cloud Federation Automation & Efficiency Explosive community growth Developers

Conference Attendees

Latest release created by >200 Developers from 55 companies worldwide Users of OpenStack User stories

We wanted our internal users to be able to create their own servers, virtual machines, storage, and networks. They’d be able to provision themselves instantly with what they needed without having to wait for a system administrator. – Mariano Guelar, infrastructure manager at MercadoLibre

Our storage demands have been doubling every eighteen months. If your data are worth keeping, then they’re worth keeping online and sharing. – Stephen Meier, SDSC Storage Platforms Manager The core of OpenStack

OpenStack Capabilities Project Codename Virtual Machines: provision & manage large pools of on- Nova demand computing resources Virtual Block Storage Devices: Volumes on commodity Nova (now Cinder) storage gear, and drivers for more advanced systems like NetApp, Solidfire, and Nexenta Object Storage: petabytes of reliable storage on standard gear Swift Virtual Networks: VLAN or Flat Network, automation coming Nova (now Quantum) with Quantum project (Folsom Release fall 2012) Web Dashboard: self-service, role-based web interface Horizon Middleware: multi-tenant Identity Management that ties to Glance, Keystone existing stores (e.g. LDAP) and Image Service The development process

 Open development  Decisions are taken by technical leads, elected  Design summit to define the roadmap  Time based release cycle  Every 6 months, in April and September  Open source  Apache Software License v2 How to get started

DISTRIBUTIONS DEVSTACK TRYSTACK.ORG Solution to the puzzle Lahnam Napier, CEO Rackspace Rides a tractor for fun Chris Kemp Gen. Pete Worden former NASA CIO Nicknamed Darth Vader CEO Nebula Hired Chris Kemp at NASA co-founder of OpenStack

The near future

2800 cores per rack 5 Watts per board 1.5W if idle

Thank you …

 Stefano Maffulli  @smaffulli on Twitter  stefano@.org  … for supporting OpenStack!  @openstack

All text and image content in this document is licensed under the Creative Commons Attribution-Share Alike 3.0 License (unless otherwise specified). "LibreOffice" and "The Document Foundation" are registered trademarks. Their respective logos and icons are subject to international copyright laws. The use of these therefore is subject to the trademark policy.