OpenStack, The birth of the Open Cloud

OpenStack:The birth of the Open Cloud

Alvaro Lopez OrtegaEngineering ManagerCloud Infrastructure - Red Hat

Introduction

Let's begin from the beginning

Allow to introduce myself and I'll be talking about today

I've been building scalable systems for the last 10 years, as well as the teams that are responsible for managing those systems.

Huge Open Source enthusiast. When things really get rough you're only in control of you own fate if youcan dive into the source code.

So without farther delay, I'll introduce Cloud Computing, and OpenStack.

Cloud Computing, the paradigm

Cloud Computing. Delivery of computing as a service rather than a product

Generator

Initial investment

Install it

Fuel it

Service it

If it broke your business would go down

Whole lot of definitions

To me, it isn't more than to deliver computing as a service (rather and as a product)

It isn't the 1st time this shift in technology happens. Think of Electrocity, for instance

Cloud Computing, the paradigm

Cloud Computing. Delivery of computing as a service rather than a product

Electric Grid

Plug into the grid

You're done!

EaaS

Electricity as a Service!!
How utterly cool is that?

Virtualization

Before

After

Consolidation of Hardware
Fewer, bigger servers

Workload management
Over-subscribed services get more hardware

App protection
Fault tolerance, High Availability & Live migration

Scalability
Add resources to VMs on the fly

Pets vs Cattle (yes, again)

Scale Up- Servers are like pets

Scale Out

- Servers are like cattle

Pets are given names, are unique, lovingly hand raised and cared for. When they get ill, you nurse them back to health.

Cattle are given numbers and are almost identical to each other. When they get ill, you get another one.

Do you remember when we used to name servers? We used all sort of names: planets, sesame street characters, NBA players, planets, the Simpsons, etc.

All that is long gone, isn't it?

Instance types

Server 1923432 cores60GB memory

Server 1923532 cores60GB memory

XL16 cores30 GB memory

L

L

XL

L

M

M

Utilization is key

Different instance sizes

Fully utilize physical servers

Here is where the cost come into play

The Open Cloud

The Open Cloud

All about Freedom
You'll be only in full control of your fate if you can dive deep into your infrastructure source if something goes wrong.

No more lock-in
Breaks out from the lock-in of a proprietary cloud platforms

Interoperability
Use of widely adopted open standards

Free Software / Open Source

What is OpenStack?

Software stack to build IaaS solutions

Free Software released under the ASL 2.0

Implemented in Python

6 months release cycle

Run by a community of contributors

Modern and solid development model

Managed by the OpenStack Foundation

How OpenStack was born?

Spring 2010

NASA and Rackspace

Common targets

First release October 2010

2012, August 2012: Red Hat OpenStack

September 2012: OpenStack Foundation

October 2012: Havana released

NASA: Nova, networking, volumes

Rackspace: Swift

To play it fare
Not the only Open Cloud platform.

Open Cloud technologies (users)

CY13-Q3, OpenSource IaaS community analysis - Qingye Jiang

Active Participants in the community

Open Cloud technologies (users)


Global size of the different communities

On the development front - very similar trend

Open Cloud technologies (development)


Monthly commit (changes)

Big increases in activity when a release approaches

Open Cloud technologies (development)


People contributing code

OpenStack is sky rocketing!

Let me clarify something about the OpenStack releases and the name convention that we follow

OpenStack Releases

Grizzly Released: April 2013

Bear of the State of California's flag

Havana Released: Oct 2013

Unincorporated locale in Oregon, US

Icehouse Release: ~April 2014

Street in Hong Kong

Consecutive initial Letters

Short names

Named after somewhere close to the venue of the OpenStack Summit

OpenStack Architecture

Don't be confusedIt's a powerful and complex system


The conceptual design isn't a tough to comprehend

Let me briefly introduce you the main components in OpenStack


Modular architecture

Designed to easily scale out

Based on (growing) set of core services

- Modular Architecture

- Designed to scale out

- Growing set of core services


User information, Tenants, Roles, etc.

Policies Enforcement

Service catalog

Backends: LDAP, SQL and Key Value Stores

- Holds information about users, tenants, roles

- Policies enforcement

- Service catalog

- Backends: LDAP, SQL, Key Value Stores


Block devices exposed to compute instances (bootable)

Independent life cycle from VMs

Support for backups and Snapshots

Several backends: GlusterFS, NetApp, EMC, etc..

- Block devices exposes to Vms

- Independent from VMS life cycle

- Backends: GlusterFS, NetApp, EMC, etc


Neutron formerly known as Quantum

API for networking on OpenStack - Provides connectivity to VMs

Decouples physical and logical view of the network

Multiple backends: OpenFlow, Linux Bridge, etc..

- Neutron, formerly known as Quantum

- API for networking

- Provide connectivity to Vms

- Decouples physical and Local view of the network

- Backends: OpenFlow, Linux Bridge, Cisco, ...


Generic Object storage

Highly Scalable + Multiple Redundancy

Store & Retrieve files through REST interface

Kind of like Amazon S3 storage

- Generic Object Storage

- Highly Scalable

- Multiple Redundancy

- Store and Retrieve thru RESTful interface

- Kind of like Amazon S3


Image storage and metadata index

Images are stored in Swift or GlusterFS

Disk formats: raw, qcow2, VHD, vmdk, vdi, aki, ari, ami

Container formats: ovf, bare, aki, ari, ami


Interface to Hypervisors

Starts, Stops and Migrates VMs

AMPQ broker to communicate with the other components

Backends: KVM, Xen, Qemu, ..

- Interface to Hypervisors

- Starts, Stops, Migrates VMs

- AMPQ broker to communicate (Qpid)

- Backends: KVM, Xen, Qemu, etc


Horizon: The framework

Dashboard: The UI reference implementation

Folsom supported Nova, Cinder, Glance, Swift

Grizzly added support for Neutron (basic)

Two parts

- Horizon: The framework to build interfaces

- Dashboard: UI reference implementation (Django)

- Evolution - Folsom: Nova, Cinder, Glance and Swift - Grizzly: Basic Neutron - Havana: Greatly improved Neutron support

Open nature of OpenStackMany different technology options. Survey.

OpenStack Community Survey (Oct 2013)

- Storage: LVM

- Deployment tool: Puppet

- Network driver: OpenVswitch

- Hypervisor: KVM

- Identity: SQL

- OS: Ubuntu and RedHat OSes

Community

Truly Amazing Community

Involved my many successful Open Source projects:GNU

GNOME

OpenSolaris & OpenJDK

Cherokee

Never saw a project like this.

Growth speed is unprecedented

Outstanding development model

Intro the development model still evolving

OpenStack's Community

- Large clusters testing the code once and again

- Platforms and OSes - Versions - Deployment methods - Configurations

A change will only make it when all those tests are successful and other developers bless it.

- Code in the open (mainly GitHub)

OpenStack's growing community

Number of authors has grown by 360%

Number of commits has grown by 325%

Evolution in the last 2 years:

Analysis by

- Number of authors more than tripped

- As well as the number of commits

OpenStack's growing ecosystem

Number of companies has grown by 250%

Analysis by

Companies backing up the project raised by 250%

Currently more than... wait for it.. 150


- Different companies have different roles and involvement the project

- Graph represents somehow the global contribution of the Top 10 companies

- I'm really proud Red Hat is investing so much resources in the development and support of OpenStack.


Analysis by

Bugs closed for OpenStack Havana

- Here you have another example

- Closed bugs in the latest release of OpenStack

- We do believe in Open Source, and therefore we invest on it.

You have to put your money where your mouth is, right?

Deploy OpenStack isn't easy. For that, Red Hat has also made a big effort creating RDO.

RDO

Distributions of OpenStack

OpenStack project focused on source code

OpenStack is a toolbox for creating clouds

Integration, installation, configuration, deployment are left to the user or distributor

What is RDO?

RDO is a freely-available, community supported distribution of OpenStack, packaged and integrated for Red Hat Enterprise Linux and its clones, and for Fedora

http://openstack.redhat.com/

How to deploy RDO

Install RDO release RPM

Install openstack-packstack

Run packstack

http://openstack.redhat.com/Quickstart

How to deploy RDO

Install RDO release RPM

Install openstack-packstack

Run packstack

THANK YOU!

Questions?

http://openstack.redhat.com/

Alvaro Lopez Ortega

[email protected]@gnu.org

@alobbs

Click to edit the title text format

Click to edit the outline text format

RED HAT CONFIDENTIAL | ADD NAME

Click to edit the outline text formatSecond Outline LevelThird Outline LevelFourth Outline LevelFifth Outline LevelSixth Outline LevelSeventh Outline LevelEighth Outline LevelNinth Outline Level

Technology

OpenStack, The birth of the Open Cloud