red hat
customer
convergence

#rhconvergence

forests and trees

how to look at openstack

Jamie Duncan

Sr. Technical Account Manager

@rh_jduncan

jduncan@redhat.com

804.343.6086

20141002

toronto, ontario

boiled down

If you don't adopt it, you will regret it later. If you do adopt it, you will regret it now.

                                                 Rodrigo Flores @RFFlores

agenda

From Above - A Forest

From Below - Trees

Component Overviews

Today / Ground Rules / Scope

Conclusions

OpenStack and Red Hat

Next Steps

scope

OpenStack is a platform designed to act as a huge swath of your IT infrastructure. Because of that...

There is no way we can cover that in-depth in 60 minutes. We probably couldn't do it in 60 hours if we started getting into the eccentricities of your needs and topologies.

The goal today is to make you comfortable talking about OpenStack, and to shorten your learning curve when you start to build out your depth of knowledge on it.

ground rules for today

today is a discussion, not a lecture.

openstack is massive and iterates INCREDIBLY FAST. THERE MAY WELL BE CHANGES BETWEEN TODAY'S REALITY AND THE REALITY WHEN I 'WENT TO PRESS'. I TRY TO KEEP THIS UP TO DATE, BUT TO ERR IS HUMAN.

IN THE END, IT'S ABOUT HAVING A LITTLE FUN AND GETTING A LITTLE SMARTER. LET'S DO THAT.

about jduncan

I live in Richmond, Virginia.

 

for ~3 years.

I am a big F1 fan. #teamlh

fanboy.

I am a fan of

I grew up a Flyers fan. Sorry about Ron Hextall.

@rh_jduncan | jduncan@redhat.com

I've been at

I'm a

view from above

OpenStack is built out from a group of services that split up the work that has to happen to create a true cloud environment.

The primary source of inspiration was Amazon Web Services (AWS). As you get used to OpenStack you will notice similarities in vocabulary and functionality.

a word of warning...

Before we start the Component Overviews, know that they contain a lot of buzzwords.

I will try to combat this by making a series of small, bad jokes as we progress.

These are typically very bad jokes. 

I will alert you if it's the most important part of the talk.

Horizon

One GUI to Rule Them All

The Dashboard service provides a graphical user interface for end users and administrators, allowing operations such as creating and launching instances, managing networking, and setting access controls. Its modular design allows interfacing with other products such as billing, monitoring, and additional management tools. The service provides three basic dashboards: user, system, and settings.  

It looks a lot like ...

nova

The Brains of the Operation

The Compute service is the heart of the OpenStack cloud by providing virtual machines on demand. Compute schedules virtual machines to run on a set of nodes by defining drivers that interact with underlying virtualization mechanisms, and exposing the functionality to the other OpenStack components.  

Compute interacts with the Identity service for authentication, Image service for images, and the Dashboard service for the user and administrative interface. Access to images is limited by project and by user; quotas are limited per project. The Compute service is designed to scale horizontally on standard hardware, and can download images to launch instances as required.  

keystone

Who arrrre you? I Really Wanna' Know.

The Identity service authenticates and authorizes OpenStack users; the service is used by all OpenStack components. The service supports multiple forms of authentication including user name and password credentials, token-based systems, and AWS-style logins (Amazon Web Services). 

The Identity service also provides a central catalog of services and endpoints running in a particular OpenStack cloud, which acts as a service directory for other OpenStack systems.

Multiple services can be used as  the backed, including Active Directory, Red Hat Directory Server, Red Hat Identity Management, and OpenLDAP

glance

The Image service acts as a registry for virtual disk images. Users can add new images or take a snapshot (copy) of an existing server for immediate storage. Snapshots can be used as back up or as templates for new servers. Registered images can be stored in the Object Storage service, as well as in other locations (for example, in simple file systems or external web servers).  

Supported Image Formats
raw (unformatted)
aki/ami/ari (amazon kernel,machine,ram images)
iso
qcow2 (qemu/kvm - supports CoW)
vhd (hyper-V)
vdi (qemu/VirtualBox)
vmdk (vmware)
ovf image containers

family albums? nope, AMIs and QCOW2s

neutron

Software-Defined Networking

The OpenStack Networking service handles the creation and management of a virtual networking infrastructure in the OpenStack cloud. Elements include networks, subnets, and routers; advanced services such as firewalls or virtual private networks (VPN) can also be used.  

Because the OpenStack network is software-defined, it can easily and quickly react to changing network needs

cinder

The Block Storage (or volume) service provides persistent block storage management for virtual hard drives. Block Storage allows the user to create and delete block devices, and to manage the attachment of block devices to servers. The actual attachment and detachment of devices is handled through integration with the Compute service. Both regions and zones can be used to handle distributed block storage hosts

Can be backed by multiple storage backends, including Red Hat's Gluster and Ceph

I wish I had a good masonry joke

swift

The Object Storage service provides a storage system for large amounts of data, accessible through HTTP. Static entities such as videos, images, emails, files, or VM images can all be stored. Objects are stored as binaries on the underlying file system (using metadata stored in the file’s extended attributes, xattrs). The service's distributed architecture supports horizontal scaling; redundancy as failure-proofing is provided through software-based data replication.  

like an unladen swallow

Extremely well-suited to multiple data center distribution due to nature of the topology.

Can be backed by multiple storage backends, including Red Hat's Gluster and Ceph, and Amazon's S3

ceilometer

The Telemetry service provides user-level usage data for OpenStack-based clouds, which can be used for customer billing, system monitoring, or alerts. Data can be collected by notifications sent by existing OpenStack components (for example, usage events emitted from Compute) or by polling the infrastructure (for example, libvirt).  

Telemetry includes a storage daemon that communicates with authenticated agents through a trusted messaging system, to collect and aggregate data. Additionally, the service uses a plug-in system, which makes it easy to add new monitors.  

Cloudforms is a great extension of this component. hint hint...

heat

The Orchestration service provides a template-based way to create and manage cloud resources such as storage, networking, instances, or applications.  

Templates are used to create stacks, which are collections of resources (for example instances, floating IPs, volumes, security groups, or users). The service offers access to all OpenStack core services using a single modular template, with additional orchestration capabilities such as auto-scaling and basic high availability.

Cloudforms is a great extension of this too... hint hint.

Trove

Databases As Your Service

Trove is Database as a Service for OpenStack. It's designed to run entirely on OpenStack, with the goal of allowing users to quickly and easily utilize the features of a relational or non-relational database without the burden of handling complex administrative tasks. Cloud users and database administrators can provision and manage multiple database instances as needed. Initially, the service will focus on providing resource isolation at high performance while automating complex administrative tasks including deployment, configuration, patching, backups, restores, and monitoring.

Trove is currently very new and young. We want to mention it here because it also has the potential of being very awesome.

looking up from below

The view for an engineer who is managing an OpenStack installation (large or small) isn't quite as easy to comprehend.

Each component talks to multiple other components using RESTful APIs

Users connect to Horizon and their systems using similar API calls along with standard services like HTTPS, VNC, and others.

A more accurate infographic would look like ...

aN api for everything

and for every service a RESTful API

Each core service within OpenStack uses RESTful APIs to communicate with one another.

A positive is that any service can be located just about anywhere as long as it can communicate via HTTPS to the other services it needs to make OpenStack functional.

A negative is that the possible ways to build OpenStack involves math that I am not comfortable with ... or even able to really understand at a fundamental level.

focused on the upstream

OpenStack has a million moving parts, and all of them are developing incredibly quickly.

Red Hat has been a member of the OpenStack community since 2011.

Our developers are everyday leaders for both governance and technology components, including several team leaders.

Up to the minute statistics at 

http://activity.openstack.org/dash/browser/

community facts

OpenStack is the source-code only. Not fleshed out installers.

Releases on a 6 month cadence

2 - 3 'snapshots' including bug fixes

No fixes or snapshots after the next release

rdo 

RDO is a community version of OpenStack packaged and tested for RHEL 6 and RHEL 7

RDO Quickstart makes it easy to get up and running as a test bed

No registration required

Closely follows the upstream release cadence

6 month lifecycle - limited updates based on upstream

Binaries created from the upstream source

ready for production

Enterprise Linux OpenStack Platform is a hardened OpenStack implementation

3 year lifecycle beginning with Havana.

fully supported by Red Hat Global Support Services

Released 2-3 months after upstream on average

Lifecycle will continue to increase based on upstream stability and resources

hypervisor support

Red Hat Enterprise Linux OpenStack Platform supports multiple hypervisors.

lightweight / small footprint

low overhead

small attack surface

cost-effective

massive scale-out

co-exist with existing stuff

seamless migration

use Neutron with NSX

ESXi not supported

guest support 

All 32-bit and 64-bit RHEL from 3 through 6

32-bit and 64-bit Suse Linux Enterprise Server 10 and 11

Windows XP SP3+ 32-bit
Windows 7 and 8 32-bit and 64-bit
Windows Server 2003 SP2+  32-bit and 64-bit
Windows Server 2008 R2 64-bit
Windows Server 2012 64-bit

Red Hat supports multiple versions of multiple operating systems running inside of OpenStack. We still can't help you fix Windows, but we can give you a great cloud to run it on.

kicking the tires

Getting started with OpenStack and Red Hat is easy

Get a 90-day evaluation of Red Hat Enterprise Linux OpenStack Platform

redhat.com/openstack/evaluation

Get with your account representative and ask them about our Red Hat Cloud Infrastructure product

redhat.com/cloud

Get a copy of RDO and start contributing to the Open Source Community

openstack.redhat.com/get_involved

 

conclusions

With OpenStack, you no longer have to tailor your workflows to account for what is available on one platform or another.

Images vs. Dynamic Kickstarts

disk image formats

proprietary networking methods

openstack is scalable in ways no hypervisor-centric cloud solution can be.

the ability to offload components and scale them as required

speed of expansion is phenomenal 

the ability to exist in multiple datacenters truly as a single cloud

you grow the parts you need when you need them

next steps

go forth and conquer!

try it out with RDO, the source from github, or any of the other ways you can get the bits

ask anyone on your Red Hat team your fun and interesting OpenStack questions

any other questions or concerns?

Now is a good time...

good reads

Forests and Trees - RHCC - Toronto

By Jamie Duncan

Forests and Trees - RHCC - Toronto

How to look at OpenStack from both sides

  • 1,134
Loading comments...

More from Jamie Duncan