Cisco and OpenStack - Open Grid Forum...OpenStack on Cisco hardware solutions • Building or offering a “Cisco distribution” of OpenStack for distribution to our customers* •

© 2011 Cisco and/or its affiliates. All rights reserved. DRAFT DRAFT DRAFT Cisco Confidential 1

Cisco and OpenStack

Rick ClarkOffice of the Cloud CTOJuly 2011


Who Am I?


What is OpenStack?


OpenStack Mission

“To produce the ubiquitous open source cloud computing platform that

will meet the needs of public and private cloud providers regardless of size, by being simple to implement

and massively scalable.”


OpenStack TechnologyToday (Cactus release)Compute Service (Nova)Object Storage Service (Swift)Image Service (Glance)

Network Services (Diablo release)L2 Topology (Quantum)Containers (Donabe)IPAM (Melange)

AlsoIdentity (Keystone – Diablo release)Queuing Service (Burrow)Load Balancer Service (proposed)Database Service (proposed)

Releases• Cactus (Q1 2011)• Diablo (Q3 2011)• Essex (Q1 2012)


OpenStack Design Tenets• Scalability and elasticity are our main goals• Any feature that limits our main goals must be optional• Everything should be asynchronous

• If you can't do something asynchronously, see #2

• All required components must be horizontally scalable• Always use shared nothing architecture (SN) or sharding

• If you can't Share nothing/shard, see #2

• Distribute everything• Especially logic. Move logic to where state naturally exists.

• Accept eventual consistency and use it where it is appropriate.• Test everything.

• We require tests with submitted code. (We will help you if you need it)


The Four Opens


Open SourceWe will not produce "open core" software.

We are committed to creating truly open source software that is usable and scalable. Truly open source software is not feature or performance limited and is not crippled. There will be no "Enterprise Edition".

We use the Apache License, 2.0.

OSI approved,GPLv3 compatibleDFSG compatible


Open Design

We are committed to an open design process. Every six months the development community will hold a design summit to gather requirements and write specifications for upcoming release. The summits, which are open to the public, will include users, developers, and upstream projects. We will gather requirements and produce an approved roadmap used to guide development for the next six months.


Open Development

We will maintain a publicly available source code repository through the entire development process. This will make participation simpler and will allow users to follow the development process, and participate in QA at an early stage.


Open CommunityOne of our core goals is to produce a healthy, vibrant developer and user community. Most decisions will be made using a lazy consensus model. All processes will be documented, open and transparent.

We make the following promises:

● The community will be involved in the design process. You can help make this software meet your needs.

● The community will have representation on the technical board, which has the ability to override decisions by the project lead.

● This will always be truly free software. We will never purposefully limit the functionality or scalability of the software to try and sell you an "enterprise" version

● All project meetings will be held in public IRC channels and recorded.


Open Source Is Where “Standard” Cloud Infrastructure Will Be Defined

[O]pen standards [require] multiple providers, access to code and data, [and] interoperability of services. Whilst open standards provide part of the solution, it is critical…that a common reference model (i.e. running code) is provided.

[T]he obvious solution is an open source reference model as the standard. Potential examples of such would be the OpenStack effort.

-Simon Wardley, CSC

From “A Question of Standards”http://blog.gardeviance.org/2011/04/question-

of-standards.html


Asynchronous eventually consistent

communication

REST-based API

Horizontally and massively scalable

Hypervisor agnostic: support for Xen ,XenServer, Hyper-V, KVM, UML, LXC, and ESX Hardware agnostic:

commodity hardware, RAID/SAN not required

OpenStack Compute Key Features


REST-based API Data distributed evenly throughout system

Hardware agnostic: standard hardware, RAID not required

No centraldatabase

Scalable to multiple petabytes, billions of objects

Account/Container/Object structure (not file system, no nesting) plus Replication (N copies of accounts, containers, objects)

OpenStack Object Storage Key Features


OpenStack Community Ecosystem


The Good the Bad and the Ugly


Quantum

Quantum API

Quantum Service• L2 network abstraction definition and management• Device and service attachment framework• Does NOT do any actual implementation of

abstraction

Quantum Plug-in API

API Extensions

Vendor/User Plug-In• Maps abstraction to implementation on physical network

• Makes all decisions about *how* a network is implemented• Can provide additional features through API extensions


Quantum Architecture

Plug-in API

Quantum API Open Source + vendor extensions

Proprietary or Open SourceVendor/User Plug-in

Default Cisco Nicira Juniper

Nexus 1kv, 7k OverDrive UCS Mgr Device/Service

Extensions

Quantum


Quantum Network AbstractionFocused on L2 for Diablo Release

VM VM VMLoad

BalancerFirewall Gateway

Entities

Network

VIF VIF VIF VIF VIF VIF

Port Port Port Port Port Port

Attachments


DonabeConcept--Exact Architecture TBD

Donabe Container Service• Defines sets of elements to be deployed and managed as a unit• Defines elements, connectivity and policy, and interacts with other OpenStack services

to realize the container implementation• Initial implementation builds on work Cisco has done on network containers• Will expand to include all OpenStack elements (compute, storage, etc)

Nova Compute Service

Nova API

Swift Storage Service

Swift API

GlanceImage

Service

Glance API

QuantumNetworkService

Quantum API

“Other”Service

“Other” API

Donabe API


DonabeFocus on Network Container for Diablo Release

NetworkContainer

NetContainer

VirtualNetwork

NetworkContainer

QuantumNetwork

NC Templates

NetworkServices

NetworkServices


Why is OpenStack important to Cisco?


Current Infrastructure-as-a-Service is a Problem

ComputeService

(VMs, Memory,

Local Disk)

StorageServices

(Block, Massive

Key-value store)

User and System Admin

Basic Network Connectivity

Developer API

Servers Disks Accounts

Issue: networking is limited to basic connectivity. Impossible to create multi-tier applications. Reduces network to commodity. Dependent on Cloud Stack software vendors to express our value. Limited ability for applications to take advantage of network services.


Network Services Enable Developer Solutions

User and System Admin

Network Connectivity

Developer API

ComputeService

(VMs, Memory,

Local Disk)

Servers

StorageServices

(Block, Massive Key-value store)

Disks

NetworkServices

(Subnets, Network

Svcs, Security)Virtual

Networks

Network APIs

² Create-network(“L2”)² Attach-vm-to-network(vnet-a)² Attach-service-to-network(vnet-b)


Essential Infrastructure for Building Clouds

Solutions for Deploying Cloud

Services

Innovation to Accelerate Use

of Clouds

OpenStack Fits Into Our Strategy


There is demand for OpenStackThere are public

OpenStack successes today:

…and interest in OpenStack is exploding.


What is Cisco Doing With OpenStack?


What Cisco is doing:

What Cisco is NOT doing:

• Leading the design and development of network services and abstractions that allow extension and innovation by Cisco and others

• Demonstrating the deployment and operation of OpenStack on Cisco hardware solutions

• Building or offering a “Cisco distribution” of OpenStack for distribution to our customers*

• Integrating OpenStack into any existing product or service for sale to customers*

* This could change in the future. However, our participation in OpenStack should be carefully positioned with customers, partners, press and analysts.


Leadership in Key Network Services

Quantum• Simple L2 network abstraction manager

• Manages VM and network service connections within an address space.

Donabe• Simple container creation and management

• Initial focus on network containers, but will expand to include compute, images, storage, etc.

Melange• Basic IP address management service (IPAM)

Cisco F

ocus

Nova/Swift/Glance Refactoring

• Rework networking logic within Nova to support NetStack

services• Possible reworking

of provisioning scheduler to

support use of network data in

placement decisions.


OpenStack and Cisco Technology


Objective 1: OpenStack On CiscoToday

Unified Fabric

Unified Computing

Unified NetworkServices



GlanceImage

Service


DonabeContainer

Service

Cisco Intelligent Automation / Newscale


Objective 2: OpenStack Drives Cisco

Quantum API

Quantum Service

Quantum Plug-in API

API Extensions

Cisco Cloud Networking Plug-In

Overdrive (Linesider) Cloud Centric Networking

Cisco Infrastructure Products

Unified Fabric

Unified Computing



Objective 3: Cisco Integrates OpenStack

Overdrive (Linesider) Cloud Centric Networking

Cisco Infrastructure Products

Unified Fabric

Unified Computing




GlanceImage

Service


DonabeContainer

Service

OpenStack Distribution

Cisco Intelligent Automation / Newscale



What is OpenStack?Open-Source Cloud Computing Project – Apache 2.0 Licensing

Originated at NASA, with Rackspace

Growing support from vendors (Cisco, Dell, NetApp, Citrix, Intel, Microsoft, Brocade, etc.) – 60 companies

Three existing projects:

§ OpenStack Image Service – Manage Images

§ OpenStack Compute – IaaS Compute

§ Open Object Storage – IaaS Storage

Currently focused on IaaS services, may expand to PaaS frameworks

“Network” area still being defined OpenStack Object Store(Storage)

OpenStack Compute(VMs & VM Networks)

OpenStack Image Service (Image Library & Management)

Network


Markets – Growing interest in Cloud Computing from Service Providers, Enterprise and Government.

Early Customers – NASA, AT&T (internal), Activison/Blizzard, NTT Data, Rackspace Cloud Servers

Market Competitive Trends – Hypervisors and Cloud Management treat the Network as “commodity infrastructure”. Need to insert better ways to Cisco infrastructure.

Competition (vendors) - Dell: prototype provisioning tools (Enterprise / SP) - Citrix: “OpenCloud” architecture (NetScaler, NetCache) - Brocade: announced support at recent launch

Open Source Trends / Threats – OpenCompute, OpenStack (IaaS), Open Source PaaS (Cloud Foundry, etc.)

Why is Cisco involved in OpenStack?


Consolidation Automation

GoldPlatinum

Virtualization

Journey to Cloud Computing

Documents

Cisco and OpenStack - Open Grid Forum...OpenStack on Cisco hardware solutions • Building or offering a “Cisco distribution” of OpenStack for distribution to our customers* •