OpenStack Meetup Amsterdam 17-4-2014

1

OpenStack in real life

Bart van den HeuvelOpenStack Meetup

Amsterdam

through red glasses

2

Installing OpenStack in EMEA

Part of Red Hat Architects team

Seeing the world through through Red Glasses

My work as Forward Deployed Engineer

3

A success story for OpenSource!

Very steep learning curve

A lot of technologie combined

So many choices, so many are good,just a few combine well

Very much like Linux 20 years ago

4

Some organizations don't know what they are in to

OpenStack the hype!!!!!1111!!!

OpenStack not virtualisation? What?!!?!

Is it then a orchestration tool for my other cloud components?

Pets vs Cattle

Upgrading your instance OS? NO!!!

A different kind of architecture...

TRADITIONAL WORKLOADS

● Stateful virtual machines

● Big VMs: vCPU, vRAM, local storage inside VM

● Application SLA aligned to VM itself

● Relies on underlying HA technology to meet SLA goals

● VMs scale up: add vCPU, vRAM, etc.

● Applications not designed to tolerate failure of VMs

CLOUD WORKLOADS

● Stateless VMs, application distributed

● Small VMs: vCPU, vRAM, storage separate

● Application SLA not dependent on any one VM

● Many instances can provide application availability

● Applications scale out: add more VMs

● Applications designed to tolerate failure of VMs

So... What then?

With Virtualization you concentrate on one, two or more virtual machines

With OpenStack cloud you expand that focus to your software defined datacenter

What about workloads

Cloud workloads?

- Unpredictable load or potential for explosive growth

- Partial utilization

- Easy parallelization

Typical OpenStack Use Cases

● Service provider offering● Re-sell compute, networking and storage resources as a new

cloud provider to other organisations

● Internal cloud offering● “Infrastructure-on-demand” service for internal customers● Test & Development Environments

● Large-scale web applications or content farms● Dynamically scale based on load● e.g. Netflix, PayPal, eBay

But i want the OpenStack

- stateless distributed processes

- Can't i run VM's like in the old days?

- Legacy workloads

Controlling vsphere with Nova

Which organisations should use OpenStack?

Automation, automation, automation

Options for the people....

Open Source Tech Guru's, using and contributing upstream

Open Source enthusiasts, using upstream as is.

Consumer plususing packaged solution, expecting support and help contributing upstream

● Pure Consumerusing as is; expecting support, training and consulting services

So many options

Using upstream directly from trunk

Using a packaged but unsupported version

Using a vendor supported product

And more options...

Installing from trunk, devstack, elbow grease

Installing by hand, using packages

Going fully automatic

What is Red Hat's view?

- Packages

- Puppet modules

- Packstack

- The Foreman / Satellite 6

- TripleO / Tuskar

Red Hat makes 'sensible' choices

- Package the projects

- Define a working method, upstream

- define a HA strategy

- Integrate with other products, including those from other vendors

HA in OpenStack

- Load balancing, haproxy / Keepalived

- Not all services are stateless

- The MySQL debacle

- Shared storage