Using Crowbar to Deploy Your OpenStack Cloud

Adam Spiers

Vincent Untz

John H Terpstra

2

Clouds don’t comeClouds don’t comewith an auto-pilot with an auto-pilot

3

IT Problem: Scale Explosion

Mainframe Client / Server Datacenter Cloud

1980 1990 2000 2010

4

Chances they all have the same settings?

5

IT Problem: Complexity ExplosionSimple Conceptual View

6

IT Problem: Complexity Explosion

7

• Manual and “hand-crafted”

• Tightly bound to individual skills

• Reproducibility?

• Quality? High defect/error rate

• Magic configurations

• Expensive and slow

IT Today: Stuck Pre-Industrial Revolution

Manufacturing before the Ford Model-T

8

• Use machines instead of manual labor

• Assemble with standardized parts

• Break large and complicated processes into smaller and easier sub-processes

• Apply specialized and general labor accordingly (engineers vs. assembly workers)

• Deliver agility and responsiveness

IT Needs an Industrial Revolution

Apply industrialized processes to IT operations

9

Cloud service Management

Business support

Provisioning/Conf

Portability/Interoperability

Configuration

Customer Mgmt.

Account/Billing

Pricing/Audit

Inventory

Provisioning

Metering

Inventory

Service Layer (IaaS)

Image Object Network

Compute Volume Identity

Resource Abstraction Control LayerStorage

Virtualization

Network Virtualization

Operating System

Hypervisor Resource Allocation

MonitoringAccess Control

Physical

HVAC Power Facility

Compute Storage Network

Clouds Do Not Operate Themselves!

10

Why use Crowbar?

• Crowbar takes DevOps to the Cloud‒ Automates infrastructure provisioning and deployment

‒ Highly customizable deployment

11

● Slow ROI● Long term maintenance ● Business liability● Not standardized● Very expensive

Hand Assembled or Homegrown

● Difficult/impossible to integrate/extend

● Vendor-lock in● Lack of ecosystem● Very costly

ProprietaryCommercial

● Some lack a successful track record

● Some limited in configuration capabilities

● Lock-in risk if developed by single entity

Other Open Source

● Narrowly focused Installers● No ability to “operate”

environment beyond install● Sales tool

OpenStack Installers

Alternatives

Juju, Razr,Xcat,Cobbler

Chef, Puppet, Cfengine

Alamo, Fuel, Airframe, Triple-O/Ironic

HP Server auto, HP Cluster Mgt. IBM Platform, StackIQ

How Crowbar Assembles the Cloud

13

CloudOps: The Cloud Frontier

• Cloud‒ Elastic and oversubscribed

• Ops‒ Stable AND dynamic

‒ Maximum utilization!

• Crowbar Benefits‒ Delivery of Cloud services

as needed

‒ Managed resilience

‒ Rapid recovery from node failures

‒ Automated and dependable DevOps and CloudOps

14

Core Concepts

• DevOps / Reference Deploy

• Open Operations / Best Practice

• Late Binding > Continuous Deploy

• Layered / Interconnected Orchestration

• Network Abstraction for DevOps

• Physical Infrastructure is Complex (Net, NIC, RAID, Admin, etc)

15

• Includes all the components required to implement an entire cloud infrastructure including ecosystem partners

• Pluggable components deploy cloud infrastructure

• Allows for addition of proprietary IP and expansion by the community services and customers

• Can integrate with existing proprietary products

• Delivers basic data center services and required cloud infrastructure.

• Provision bare-metal servers from box to cloud WITHOUT user intervention (other than racking/cabling and some minimal configuration questions)

Assembly is Layered and Ordered

Core Components & Operating Systems

Cloud Infrastructure & Vendor Extensions

Physical Resources

APIs, User Access, & Ecosystem Partners

“Cro

wb

ar”O

ps

Ma

nag

em

ent

16

Layers Beyond OpenStack

OS, Updates, Monitoring

Cloud Infrastructure

Rack, BIOS, RAID

APIs, User Access & Ecosystem Partners

Cro

wb

a r

17

Crowbar: The CloudOps Choice

• Benefits‒ Reduces deployment effort

and overheads

‒ Provides operation control model

‒ Fast: Raw server → Cloud in <2 Hours

• Proven Tech‒ Multi-node deployments

from the ground up

‒ Every node is automatically “custom built” on demand

Open Source Solution – Open Source Solution – not not Dell hardware limitedDell hardware limited

18

Crowbar Plus OpenStack“Boxes to working OpenStack in <2 hours”

• Crowbar’s birthright was as an OpenStack installer

• OpenStack is complex

• To create an OpenStack project, needed:

‒ To get cloud sites running quickly

‒ Cope with frequent updates

‒ Connect many moving parts

‒ Be part of the open source community

• Crowbar can deploy

‒ OpenStack (Grizzly, Havana)

‒ Hadoop

‒ Applications

19

• Deployment Toolset Integrator

• Bare Metal Provisioning

• SUSE Cloud Capabilities

Demo – Benefits

How Crowbar Works

21

OpenStack Orchestration: Chef and Crowbar

22

What is a Barclamp?

Barclamp

Chef RecipesO/S App

PackagesCrowbar API & Partial UI

Components & Scripts

“Cro

wb

ar”

Op

s M

an

ag

em

en

t

• Crowbar API and Partial UI‒ Adds states and transitions to Orchestration‒ Customizes UI specific to barclamp‒ Visual extensions to nodes/networks/utils

• Chef Recipes‒ DevOps description of application‒ Enforced repeatable configuration

• O/S App Packages‒ Operating system dependencies (Debs and RPMs)

• Components and Scripts‒ Ad hoc configuration not covered by Chef

23

Physical Networking in Crowbar

24

Logical Networking in Crowbar

25

Traditional Architecture

Design Blueprint Build

26

Today's Architecture

Design

Blueprint

Build

Continuous Revise/Deploy

Crowbar Development Community

28

Community

• 600 followers on Github

• 2,500+ ISO downloads in 6 months

• Active Listserv with 450 subscribers

• Key external contributions from SUSE, Intel, Mirantis, CloudBase

• Hosting two of the most active OpenStack Meetups (Austin and Boston)

http://Dell.com/OpenStack - White papers and more!http://Dell.com/Hadoop - White papers and more!http://crowbar.github.com/ Official homepagehttp://github.com/crowbar - Source code and instructions

Demo

30

• SUSE Cloud Admin Node

• The Control Node

• A Compute Node

Demo – Deployment of Crowbar

Question & Answer

Unpublished Work of SUSE. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary and trade secret information of SUSE. Access to this work is restricted to SUSE employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of SUSE. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.