build your own open source cloud

BUILD YOUR OWN OPEN SOURCE CLOUDAdrian Otto, Distinguished Architect

ON DEMAND, SELF SERVICE

CLOUDAPI + VMs + Containers + Bare Metal + Multi-Tenancy

PUBLIC CLOUD SERVICE

01: CLOUDPay a service provider, run your workloads there.

PRIVATE CLOUD

02: CLOUDYou own it, so you make the rules.

PUBLIC + PRIVATE CLOUD

03: HYBRID CLOUD

Decide what to run where, and have a consistent way to use both.

Use the r ight tool for the job

Containers

Consistent deployment to deploy your apps to a different destinations.

7

Containers

Public Cloud

Private Cloud

App

Use the r ight tool for the job

Containers

Consistent deployment to deploy your apps to a different destinations.

8

Containers

Public Cloud

App

ADRIAN OTTO

11

Outl ine

Developer Self-Service, and Enabling NextGen ApplicationsGiving your developers access to API driven infrastructure, the business case

Overview of OpenStackThe prevailing open source cloud software

Deploying OpenStackWhat tools to use to create your own cloud

ReviewQuestions and Answers

Compute, Networking, and Storage

12

OP

EN

STA

CK

S

ER

VIC

ES

IdentityImagesCompute

SDNObject StorageBlock Storage DNS Bare Metal

DashboardEncryptionTelemetry

BigDataDBaaSOrchestration Containers Queues

Layer 4: Consumption Services

Layer 3: Optional Enhancements

Layer 2: Extended Infrastructure

Layer 1: Base Compute Infrastructure

SDLC

OP

EN

STA

CK

S

ER

VIC

ES

KeystoneGlanceNova

NeutronSwiftCinder Designate Ironic

HorizonBarbicanCielometer

SaharaTroveHeat Magnum Marconi

Layer 4: Consumption Services

Layer 3: Optional Enhancements

Layer 2: Extended Infrastructure

Layer 1: Base Compute Infrastructure

Solum

BARE METALVM

DOCKER

OPENSTACK

KUBERNETES

MESOS

MAGNUM

DOCKER API

K8S API

MAGNUM OVERVIEW

Cloud operators assume a r isk when select ing a s ingle c loud technology today… but OpenStack is d i f ferent .

16

OpenStack Contr ibutor Stat ist ics

17

3,716,027

Lines of code

6437 Contributors

336 Companies

715 Projects

1107 Years of Effort

18

Outl ine





ON DEMAND, SELF SERVICE

CLOUDAPI + VMs + Containers + Bare Metal + Multi-Tenancy

WHY? BECAUSE SHADOW IT.

DEVELOPER SELF SERVICE

If you don’t offer it as a service, it’s going to happen anyway.

MICROSERVICE ARCHITECTURE

NEXTGEN APPLICATIONS

Immutable infrastructure, Container per component, 12-Factor apps

YOU KNOW YOU WANT IT(subliminal message)

22

WHY?

MICROSERVICES

Continuous deployment, efficient scale, smaller lifts to upgrade. Agility.

THE SOFT WARE DEFINED ECONOMY

EVERY COMPANY IS BECOMING A SOFT WARE COMPANY

FAST

GOOD CHEAPTOD

AY

FASTTO

MO

RR

OW

FAST FAST

UBER, THE WORLD’S LARGEST TAXI COMPANY, OWNS NO VEHICLES. FACEBOOK, THE WORLD’S MOST POPULAR MEDIA

OWNER, CREATES NO CONTENT. ALIBABA, THE MOST VALUABLE RETAILER, HAS NO INVENTORY. AND AIRBNB, THE WORLD’S LARGEST ACCOMMODATION PROVIDER, OWNS NO

REAL ESTATE. SOMETHING INTERESTING IS HAPPENING.

27

— TECH CRUNCH, MARCH 2015

AGILIT Y IS THE SHIELD FOR DISRUPTIONAnd it can also be your weapon.

28

Summar y of business case for pr ivate c loud

29

1

2

3

Shadow IT will happen if you don’t offer a developer self service option

Microservice software architecture for efficiency and agility reasons

Software defined economy means agility is essential to avoid disruption

30

Outl ine





31

OpenStack Deployment Tools

Chef RecipesIf you love chef, there are recipes for OpenStack deployment

Puppet ModulesThe traditional way to deploy a complex software system

Various Vendor SolutionsFuel, Crowbar, Redhat OpenStack Platform, etc.

OpenStack Ansible (OSA)Upstream managed project for container based OpenStack control plane using Ansible

32

OpenStack Ansible (OSA)

•Deploy OpenStack in about 30 minutes

•Services run in lightweight system containers

•Easy to upgrade

•Community designed, developed, and managed

http://docs.openstack.org/developer/openstack-ansible/

OPENSTACK MAGNUMHow OpenStack can host your microservice applications

34

What is Magnum?

• Magnum is an OpenStack API that allows the use of your keystone credentials.

• Magnum is designed from the ground-up to be multi-tenant in both the cloud’s data plane and control plane.

• Magnum allows for different container cluster types to be simultaneously run side-by-side in the same cloud account, by the same tenant.

• Clusters are isolated from each other using groups of nova instances.

• When you want to upgrade your container runtime, you simply create a new cluster.

HOW IS THIS DIFFERENT THAN JUST RUNNING KUBERNETES OR DOCKER SWARM?

An OpenStack API Service that allows creation of container clusters

35

Terminology (1/4)

COE

Container Orchestration Engine. Examples: Docker Swarm, Kubernetes, Apache Mesos.

36

Terminology (2/4)

Magnum Cluster

A Magnum cluster is an API resource in OpenStack Magnum that is composed of nova instances, neutron networks, security groups, and other resources combined using a heat stack. This is where your Container Orchestration Engine (COE) runs.

Clusters may be scaled up or down by adding or removing nodes from them. Heat facilitates the setup and scaling of Clusters.

37

Cluster Cluster Cluster

COE COE COE

Nova instance

Nova instance

Nova instance

Nova instance

Nova instance

Nova instance

Terminology (3/4)

ClusterTemplate

A ClusterTemplate is a model used for creating a Cluster resource. It contains information that is common among all clusters that are instantiated from it. Each one uses a driver that defines a cluster type (swarm, kubernetes, mesos, etc.).

38

ClusterTemplate Cluster

Cluster

Cluster

Terminology (4/4)

Native Client

The client distributed with the COE. For example “docker” or “kubectl”. A native client is not an OpenStack Client. It uses TLS to authenticate with the COE.

39

Cluster

COE

Nova instance

Nova instance

Nova instance

Native Client

TLS

Magnum Dif ferent iators

40

Fundamental Design Goal

Docker Swarm, Kubernetes, Mesos

VM or Bare Metal

SSO Experience for Cloud Users

Multi-Tenant Control and Data Planes

Choice of COE

Choice of Server Flavor

Integrated with OpenStack

getcarina.com Free Beta available today.

Why This Matters

42

1

2

3

Choice. Avoid locking into a single container orchestration tool

Speed. Easily create new container clusters in ~2 minutes

Agility. Iterate quickly on your software, and make small lifts.

43

Outl ine



Deploying an OpenStackWhat tools to use to create your own cloud


44

Review

•You may need a private cloud just as much as you need a public one. •Shadow IT will happen if you don’t offer a developer self service option •Microservice software architecture for efficiency and agility reasons •Software defined economy means agility is essential to avoid disruption

•One cloud == Myth. •Use containers as a way to deploy apps to the cloud of your choice.

•OpenStack: prevailing open source cloud software •Offers compute, networking, and storage (+715 modules for everything under the sun). •Safe to bet on OpenStack because of diverse community & no single corporate sponsor. •Offers quick and easy way to run different container orchestration environments.

•Many ways to deploy and run OpenStack •OpenStack Ansible Recommended

O N E FA N AT I C A L P L A C E | S A N A N T O N I O , T X 7 8 2 1 8

U S S A L E S : 1 - 8 0 0 - 9 6 1 - 2 8 8 8 | U S S U P P O R T: 1 - 8 0 0 - 9 6 1 - 4 4 5 4 | W W W . R A C K S PA C E . C O M | W W W . G E T C A R I N A . C O M

© RAC K S PAC E LT D . | RAC K S PAC E® AN D FAN AT I C AL S U P P ORT ® ARE S ERV I C E M ARK S OF RAC K S PAC E U S , I N C . REG I ST ERED I N T HE U N I T ED STAT ES AN D OT HER C OU N T RI ES . | W W W.RAC KS PAC E .C OM

Thank you

build your own open source cloud

Technology