1. OpenStack Installation Comparisons by Glenn Baker
10/10/2015
Thanks everyone for coming. First off I’d like the thank Haisam. He has help make all of this possible routinely. Thank you Haisam. I’d also like to thank Nexenta for joining us tonight. It is always nice to see a partner of ours at these events. We work closely with Nexenta and have had a relationship with them for some time now. (years). Thanks to Mavenspire for allowing us use their resources to contribute here. Thank you Michael, Jessica and Valerie.

2. Agenda Brief Introduction to OpenStack
OpenStack Release Tempo / Versioning
Introduction to Liberty
Installation Types & Comparisons
Questions
Input
Agenda

3. What is this OpenStack I keep hearing about?
Who is this Glenn guy?
How do know if it is right for my organization?
Introduction

4. OpenStack Quote
“OpenStack is not a cloud. It is not a project or a product. It is not a virtualization system or an API or a user interface or a set of standards. OpenStack is all of these things and more: it is a framework for doing IT infrastructure - all IT infrastructure - in as interchangeable and interoperable a way as we are ever likely to know how.”
Trevor Pott of The Register on OpenStack
Explore quote.
Source -

5. OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface.
1) OpenStack Compute: Provision and manage large networks of virtual machines
2) OpenStack Networking: Pluggable, scalable, API-driven network and IP management
3) OpenStack Storage: Object and Block storage for use with servers and applications
Talk over Horizon at high level

6. OpenStack Foundation The OpenStack Foundation promotes the
development, distribution and adoption of the OpenStack cloud operating system.
To learn more about OpenStack Foundation and OpenStack cloud software, go to:
Discuss the foundation and the value of the documentation. Encourage folks to join.

7. The OpenStack Mission
The OpenStack Mission: to produce the ubiquitous Open Source Cloud Computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable.
OpenStack is open source, openly designed, openly developed by an open community.
The OpenStack Mission (more or less the Org mission statement)
Segway to traditional OpenStack Elements slide.

8. We are in the red moon phase of OpenStack
We are in the red moon phase of OpenStack. I want to talk about how every time I look up I see the next version of OpenStack coming at us.
Depending on crowd feel take notes, continue or abandon questions. Use this as an opportunity to engage the audience and learn if they are more DEV or OPS. More Enterprise or Development.
My gut suggests a divide with a preference of hearing about both.
Who here is new to OpenStack?
Who here has Openstack Installed and if so what version?
Who has installed OpenStack for development?
Who has installed OpenStack for their enterprise?
What delivery methods did you opt for and why?
What were the issues you faced during and following your installations?

9. OpenStack Release Tempo
Highlight the release cycle pace and mention the summit.

10. Speak to some of my experiences with these versions and Segway to the Liberty release.

11. Liberty the 12th release of Openstack. Discuss news.

12. Release Date Oct 15, 2015! Today is the release day!
Key Themes of the newest release – Manageability / Scalability / Extensibility
Manageability - Common library adoption, Better configuration management, Role-based access control (RBAC) for Heat and Neutron fine tune security settings at all levels of network and API
Scalability - Initial version of Nova Cells v2 provides an updated model to support very large and multi-location compute deployments
Extensibility - Improvements in scale and performance across Nova, Horizon, Neutron and Cinder
Release Date Oct 15, 2015!

13. The “big tent” and “core services”
Discuss the Big Tent & Core Services
[1] Full list of “big tent” services :

14. Types of Openstack Installations
Public Offerings
Learning Environment
All in one (local machine)
Proof of Concept Installations
Pack Stack Modes
Enterprise Environments
Going about it on your own. Kicking the tires or just moving around the dashboard.
Local Installations on MAC or PC.
Virtual Box
Experiencing an optimized Openstack – Robust
Old Hardware
Reference Architectures
Appliance
TripleO (OpenStack on OpenStack)
Designing an OpenStack is a great achievement. It requires a robust understanding of the requirements and the needs of users to determine the best possible configuration to meet them. There is great deal of flexibility in configuration and I would like to point out a few options you have.
To design, deploy, and configure OpenStack, administrators must understand the logical architecture. A diagram can help you envision all the integrated services within OpenStack and how they interact with each other.
There are many ways to install and deploy OpenStack through
software distributions, each of which add their own value to the cloud operating
system. Software distributions powered by OpenStack include Cisco, Cloudscaling,
Debian, Fedora, Piston Cloud Computing, Red Hat, SUSE, Ubuntu and
StackOps.

15. A view of Openstack. Thanks Solinea for the SA slide.

16. The OpenStack Marketplace is a website that will help you navigate the options
The OpenStack Marketplace with allow you to make an informed decision, whether you’re building a cloud, looking to use one by the hour, or pursuing a hybrid model.

17. Discuss the options for testing in the public cloud
Discuss the options for testing in the public cloud. Mention that the marketplace is a good place to start. If you wish to discuss experiences do so. Walter Bentley and others from Rackspace.

18. Discuss the considerations of clouds in both private and public arenas.

19. Public offerings (Nebula may need removal)

20. TryStack is a free way to try OpenStack. Its an OpenStack sandbox
TryStack is a free way to try OpenStack. Its an OpenStack sandbox. That means TryStack is a testing environment only. You cannot use it for setting up your production servers. You can get a free account in TryStack by joining their Facebook group. As this is a testing facility there are several limitations in it. The server instances that you launch inside TryStack will be available for 24 hours only. You cannot upload your own server images to it, you can only select the available images in it.

21. Devstack – devstack.org – Excellent source for installation guidelines
Developer focused (Installations on local machines or vm’s that are not of an enterprise scale)
Devstack – devstack.org – Excellent source for installation guidelines
Ubuntu / Fedora / RHEL
Other OS Platforms
Types of Installations supported.
ALL-in-one Single VM
DevStack has evolved to support a large number of configuration options and alternative platforms and support services. That evolution has grown well beyond what was originally intended and the majority of configuration combinations are rarely, if ever, tested. DevStack is not a general OpenStack installer and was never meant to be everything to everyone.
DevStack is an opinionated script to quickly create an OpenStack development environment. It can also be used to demonstrate starting/running OpenStack services and provide examples of using them from a command line. The example exercises were fleshed out beyond simple examples and became useful as a quick sanity check for the OpenStack installation. That sanity check became the basis for the Gerrit gate tests for all OpenStack checkins and continues in that role until Tempest takes over. These remain as the driving priorities for ongoing DevStack development.

22. It is not an acronym or abbreviation for anything.
However, RDO does focus on building a distribution of OpenStack specific to Red Hat operating systems (and clones of Red Hat operating systems). So, in some sense you can think of RDO as being a project started by Red Hat to build a distribution of OpenStack.
The 3 letter meaningless acronym sort of comes from that line of thinking.
If you prefer, you can think of it as 'Really Darned Obvious', representing our view that it should be easy to deploy an OpenStack cloud using RDO. Or, possibly, 'Ridiculously Dedicated OpenStackers', representing our OpenStack engineering team and their passion about making this stuff work.
Just as a traditional operating system relies on the hardware beneath it, so too does the OpenStack cloud operating system rely on the foundation of a hypervisor and OS platform. RDO makes it easy to install and deploy the most up-to-date OpenStack components on the industry's most trusted Linux platform, Red Hat Enterprise Linux. and on RHEL derivatives like Fedora, CentOS, and Scientific Linux.
The OpenStack project develops code, and does not handle packaging for specific platforms. As a distribution of OpenStack, RDO packages the upstream OpenStack components to run well together on CentOS, Red Hat Enterprise Linux, Fedora, and their derivatives, and provides you with installation tools to make it easier for you to deploy OpenStack.
Packstack, an installation utility which uses Puppet modules to deploy OpenStack, is the primary tool for deploying RDO. Instructions on enabling the RDO Yum repository and installing RDO with Packstack are available on the quick start page.
RDO is a community-supported OpenStack distribution that tracks the latest version of OpenStack upstream, beginning with OpenStack Grizzly. Red Hat Enterprise Linux OpenStack Platform is an enterprise-ready commercially-supported product from Red Hat.

23. Pack Stack
Packstack is a utility that uses Puppet modules to deploy various parts of OpenStack on multiple pre-installed servers over SSH automatically. Currently only Fedora , Red Hat Enterprise Linux (RHEL) and compatible derivatives of both are supported
Packstack was created by Derek Higgins a Red Hat Software Engineer.
Packstack is a utility that uses Puppet modules to deploy various parts of OpenStack on multiple pre-installed servers over SSH automatically. Currently only Fedora , Red Hat Enterprise Linux (RHEL) and compatible derivatives of both are supported
PackStack is suitable for deploying the following types of PoC configurations:
Single-node installations, where all controller services and your virtual machines run on a single physical host. In PackStack, this is referred to as an all-in-one install.
Installations where there is a single controller node and multiple compute nodes. This is similar to the all-in-one install above, except that you may use one or more additional hardware nodes for running virtual machines.

24. Powerful configuration management tools that also serve as a deployment method

25. Heavily focused on delivery Upgrade complexity
Test deployment can be done on a laptop
Fuel as the delivery method
Easy deployment
Not free beyond test
Test environment difficult to keep running.
Some of the good and the bad .. What you mind find if you google a bit.
“Fuel really does a good job at simplifying the installation procedure required to get the OpenStack services up and running. It discovers your nodes, does a bare metal installation of either Ubuntu or CentOS, then orchestrates your installation and configuration of your OpenStack components.
Adding a node is simple, removing a node is simple. What Fuel doesn't really provide is a UI that allows you to really customize the installation. By that, I mean if you want to install API services on compute nodes, then you'd have to do that by hand.”
“We just wasted a week with a PoC trial trying to integrate with Mirantis and rather large American Telco.
Mirantis is ugly. Version 6 ships a hacked up 'Ubuntu 12.04' image with Mirantis internally backported Juno to which required they replace the Upstream Ubuntu Lib's. Including but certainly not limited to libc.
Stay far away - they use a complex set of nailgun and docker containers for their deployment scripts which are all but unusable and make assumptions (such as where Subnet range's start) which can only be changed by poking PostgresDB tables through several layers of lxc/docker container levels - i.e requiring Inception level container skills.
Consider it takes only 30mins to install ubuntu and isntall the cloud repo and copy over some precooked txt config to have the same thing Mirantis does.”

26. The Canonical Distribution is their latest offering
Juju & MAAS are used as the deployment method
Boasts record build times
Public Beta
Currently release includes 10 physical and 10 virtual machines by default.
Ubuntu OpenStack – The Canonical Distribution is the latest OpenStack offering from Canonical. It is the quickest and easiest way to build an OpenStack cloud in record time. Built on the popular Ubuntu OpenStack reference architecture, and using Canonical’s industry-leading cloud tools Juju and MAAS, The Canonical Distribution will guide you step by step from hardware provisioning to finalising your OpenStack cloud.
The Canonical Distribution is now in public beta with a limited number of options for hypervisors, networking and storage, but as we get closer to v1.0, and as more components are certified in Canonical’s OpenStack Interoperability Lab (OIL), they will be gradually added as further options. The current release includes 10 physical and 10 virtual machines by default, which should be plenty to build a test OpenStack cloud.

27. Proof of concept installations
A proof-of-concept (PoC) installation is often the next step.
PackStack is suitable for deploying to a Single node.
Installations where there is a single controller node and multiple compute nodes. This is similar to the all-in-one install above, except that you may use one or more additional hardware nodes for running virtual machines.
. in deciding whether OpenStack will work in your business environment, or simply to test its functionality. The PackStack deployment tool is a command-line utility that allows you to quickly and easily deploy a basic version of Red Hat Enterprise Linux OpenStack Platform.
Single-node installations, where all controller services and your virtual machines run on a single physical host. In PackStack, this is referred to as an all-in-one install.

28. Project Stay Puft The Foreman Openstack Installer
Remember when it was supposed to get easier?
Personal experience with the love and hate relationship with Stay puft.

29. Challenged by upgrade support
Once you have used it do you really need it?
Foreman remains behind wasn’t necessarily a bad thing.
Couldn’t be used to add compute hosts
TripleO looming in the background

30. Required knowledge of Foreman Required knowledge of Puppet
Needed a great deal of configuration knowledge
Required Kick starts
Didn't work with pre-provisioned hosts.
Integration with Satellite prevents Fuel adoption
Project abandoned
A little funny for the crowd.

31. - Cradle to Grave ownership. From OS up is engineered to run OpenStack.
- 3 Year Life Cycle Support vs 6 month life cycle
- Most certified Hardware, Software, VAR, ISV and Partners.
- Top 3 contributor to OpenStack Community
- Contribution across all the projects
Some of the highlights I’ve come to know with Redhat.

32. Ask who knows about TripleO and if they can tell you what it is?

33. What is TripleO?
TripleO is an endeavor to drive down the effort required to deploy an OpenStack cloud, increase the reliability of deployments and configuration changes - and hopefully consolidate the disparate operations projects around OpenStack.
This infrastructure includes systems to automatically install the operating system's initial configuration and later coordinate the configuration of all services automatically and centrally, which reduces both manual effort and the chance for error. Examples include Ansible, CFEngine, Chef, Puppet, and Salt. You can even use OpenStack to deploy OpenStack, named TripleO (OpenStack On OpenStack).
TripleO is an endeavor to drive down the effort required to deploy an OpenStack cloud, increase the reliability of deployments and configuration changes - and hopefully consolidate the disparate operations projects around OpenStack.
TripleO is the use of a self hosted OpenStack infrastructure - that is OpenStack bare metal (nova and cinder) + Heat + diskimage-builder + in-image orchestration such as Chef or Puppet - to install, maintain and upgrade itself.
This is combined with Continuous Integration / Continuous Deployment (CICD) of the environment to reduce the opportunity for failures to sneak into production.
Finally end user services such as OpenStack compute virtual machine hosts, or Hadoop are deployed as tenants of the self hosted bare metal cloud. These can be deployed using any orchestration layer desired. In the specific case of deploying an OpenStack virtual compute cloud, the Heat orchestration rules used to deploy the bare metal cloud can be used

34. TripleO - Defined
TripleO, OpenStack-on-OpenStack, is the project name for the OpenStack Deployment program that provides a service for automating deployments above and below the cloud. It has a common API for use in provisioning, configuring, and operating OpenStack components. A user-interface for deploying OpenStack is also available via the Dashboard application.

35. Design Guidelines
Robust automation to do CI and deployment testing of a cloud at bare metal layer
Customize generic disk images to use with Nova Bare Metal using DISKIMAGE-BUILDER
Orchestrate deployment of these images onto bare metal using HEAT
Deploy the same tested images to produc1on clouds using NOVA BAREMETAL/IRONIC Create configura1ons on disk and trigger in-instance reconfigura1ons using OS-CONFIG Clean interfaces to plug other alterna1ve implementa1ons. Ex: Use Puppet/Chef for configurations.
Slide credit to slideshare slides from other engineers. No credit of creation to myself.

36. Benefits Driving down cost through reliability
Consolidated to a single api
Golden Images – Elimination of variation
Use of Openstack prevents handoffs to other provisioning systems.
Deployments are simpler
Single tool chain to provision and deploy
Driving the cost of operations down, increasing reliability of deployments and consolidating on a single API for deploying machine images, to get great flexibility in hardware use and more skill reuse between administration of different layers.
The use of gold images allows one to test precisely what will be running in production in a test environment - either virtual or physical. This provides early detection of many issues. Gold image building also ensures that there is no variation between machines in production - no late discovery of version conflicts, for instance.
Using CI/CD testing in the deployment pipeline gives us:
The ability to deploy something we have tested.
With no variation on things that could invalidate those tests (kernel version, userspace tools OpenStack calls into, ...)
While varying the exact config (to cope with differences in e.g. network topology between staging and production environments).
The use of cloud APIs for bare metal deployment permit trivial migration of machine between roles - whether that is infrastructure, compute host, or testbed.
Using OpenStack as the single source of control at the hardware node level avoids awkward hand offs between different provisioning systems. We believe that having a single tool chain to provision and deploy onto hardware is simpler and lower cost to maintain than having heterogeneous systems.

37. How you can reach me
Business Cards – Please introduce yourself I happen to have some here with me tonight! me

39. OpenStack resources / sources
Redhat Partner Network - access.redhat.com
Opensource.com
Wiki.OpenStack.org / Docs.OpenStack.org
RDO
- Slideshares
Trystack.org
Meetup -
Ubuntu.com
Canonical.com
The Register UK
There is a lot more to be discussed and there needs to be a deeper dive and demo dive if you will. I hope to bring more in the near future.
Reaching me directly is ok / encouraged and I look forward to it.
Wrap!
Ansible!