280 likes | 797 Views
OpenStack Heat 101. Overview, Capabilities , Use Case and Demo Presented to Atlanta OpenStack Meetup March 2014. Introductions. Agenda. Jason Grimm Open Cloud Solution Architect jason.grimm@rackspace.com Mike Camp Open Cloud Account Executive m ike.camp@rackspace.com Tim Langan
E N D
OpenStack Heat 101 Overview, Capabilities, Use Case and Demo Presented to Atlanta OpenStack Meetup March 2014
Introductions Agenda Jason Grimm Open Cloud Solution Architect jason.grimm@rackspace.com Mike Camp Open Cloud Account Executive mike.camp@rackspace.com Tim Langan Enterprise Account Executive Tim.langan@rackspace.com Illyse Scheaffer Enterprise Solutions Engineer Illyse.scheaffer@rackspace.com About the presentation About the speaker Rackspace Overview OpenStack Overview Heat Background Heat Architecture Heat Operations Heat Demo Heat Group Exercise 2 2
About the Presentation • I’d rather “discuss” than “present” • Don’t be shy, please interrupt • I work for Rackspace, but this is not a sales pitch • Presenting at summit, feedback greatly appreciated • Excuse my PowerPoint (lack of) skills, slides either look like • Marketing intern with too much time on their hands • Notepad • All materials are available at: • http://jtg.grimmtheory.com/summit 3
About the Speaker Grant Park East Cobb Georgia Native Boston Key West Canton • Lots of hats… • Husband • Father • Veteran • Farmer • Racker • Architect • Lots of hobbies… • Music • Movies • Politics • Gun Collecting • Comedy • Reading Startup Co-Founder 2000-2004 Freelance Consulting 1996-2000 Mirantis Puppet / Fuel 2013 US Naval Intelligence 1992-1996 Dell Ruby / Crowbar 2004-2013 Rackspace Chef / RPC 2013-2014
About Rackspace 6,000+ RACKERS To be recognized as one of the world’s greatest service companies 210,000+ CUSTOMERS110,000+ SERVERS GLOBAL FOOTPRINTCUSTOMERS IN 120+ COUNTRIES 10 WORLDWIDE DATA CENTERS PORTFOLIOOF HOSTED SOLUTIONSDedicated - Cloud - Hybrid OPENSTACK FOUNDERLARGEST OPENSTACK CLOUD2nd Largest Public Cloud
OpenStack / Rackspace History John Dickinson Cloud Files (Swift) Swift PTL SwiftStack Co-Founder Chris Kemp Nebula (Nova) Nebula Founder PUBLIC CLOUD OpenStack Mission: “To enable any organization, regardless of size, to create and offer cloud computing services running on standardized hardware.” CLOUD STORAGE HYBRID CLOUD CLOUD FILES PRIVATE CLOUD
Rackspace Portfolio: PUBLIC CLOUD PRIVATE CLOUD DEDICATED HOSTING • Servers, storage, networking and platform services • Instantly available • Priced per hour • Custom private cloud • Powered by OpenStack • Hosted at your data center, partner data centeror at Rackspace • Bare metal servers • Dedicated VMware • Hosted Services: Exchange, SharePoint, mailgun, IIS, Apache, etc. MUTLI-TENANT & GENERALIZED SINGLE TENANT & SPECIALIZED
* Pre-July 2010 is predicated by Rackspace Cloud Files project (Swift), NASA Nebula project (Nova) OpenStack Ecosystem / History
OpenStack Project Lifecycle Open Discussion – request assistance from OpenStack contributors to add lifecycle detail Ironic project as an example: October 2013 Hong Kong Havana / Icehouse Summit April 2013 Portland Grizzly / Havana Summit September 2012 San Diego Folsom / Grizzly Summit April 2012 San Francisco Essex / Folsom Summit May 2014 Atlanta Icehouse / Juno Summit Experimental “bare metal” driver for Nova Became its own project, Independent Became a recognized “related” project Became a recognized “incubated” project Slated to become recognized as a “core” project.
Heat Described “Why ‘Heat’? It makes the clouds rise!” “The mission of the OpenStack Orchestration program is to create a human- and machine-accessible service for managing the entire lifecycle of infrastructure and applications within OpenStack clouds.” “Heat is the main project in the OpenStack Orchestration program. It implements an orchestration engine to launch multiple composite cloud applications based on templates in the form of text files that can be treated like code.” “Heat provides a template based orchestration for describing a cloud application by executing appropriate OpenStack API calls to generate running cloud applications.“
Heat Explained – Overview “Orchestration” is a great industry buzz word but what does it mean? OpenStack resource abstraction and orchestration: VM Instances Networks Routers … “Typically” Virtual (See Ironic Project) • Orchestration – “The automated arrangement, coordination, and management of complex computer systems, middleware, and services.” • Programmatic Management • RESTful API • Agnostic • Consistent • Abstracted user experience • Worlflow • AAA • Error Checking / Correction Infrastructure resource abstraction and orchestration: Compute Power Switches Block Storage … “Typically” Physical
Heat Explained – IaaS vs. PaaS Another way to look at where the Heat service fits and what it provides DBaaS VPNaaS MaaS DRUPALaaS Jason’s Mac Core Projects
Heat Main Components heat The heat tool is a CLI which communicates with the heat-api to execute AWS CloudFormation APIs. End developers could also use the heat REST API directly. heat-api The heat-api component provides an OpenStack-native REST API that processes API requests by sending them to the heat-engine over RPC. heat-api-cfn The heat-api-cfn component provides an AWS Query API that is compatible with AWS CloudFormation and processes API requests by sending them to the heat-engine over RPC. heat-engine The heat engine’s main responsibility is to orchestrate the launching of templates and provide events back to the API consumer.
Heat Architecture (Quick Overview) • Concepts to cover • Stateless (API) • Stateful • DB • MQ • Interfaces • Web-UI • CLI • API
Heat is HOT • The power of Heat is HOT (Heat Orchestration Templates) • Whatever you can do “by hand” (CLI, API, Web-UI) in OpenStack can likely be executed through a Heat Orchestration Template • Initial goal of Heat was to provide a service comparable to AWS’s “Cloud Formation” • Cloud Formation = “Service Deployment” or “Environment Deployment” • Instead of deploying a single instance, deploy all components to create a service, e.g. 2 web, 2 app, 2 db, networks, routers, etc. • Service deployment continues to be the most popular Heat use case • Autoscale also a very popular use case • Heat can leverage Ceilometer metering data and through watermarks and triggers scale
Heat Demo 23
Demo Environment Setup • Configuration notes on how this demo environment was setup • MacBook Pro • Retina, 15-inch, Early 2013 • OS X 10.9.2 • 256 GB SSD • 2.7 GHz Intel I7 (8 cores – single socket quad core /w HT) • 16 GB of 1600 MHz DDR3 • VMware Fusion 5.0.4 • Single Virtual Machine • Disk 1 – 20 GB, pre-allocated, broken into 2 GB files (OS and OpenStack) • Disk 2 – 6 GB, pre-allocated, broken into 2 GB files (Cinder-Volumes) • 4 vCPUs • 8 GB RAM • USB, camera, sound, Bluetooth, printer, video acceleration, debugging, etc. off • Hard set VT acceleration, nested hypervisor, etc. support on • Single bridged NIC • Default Ubuntu Server 12.04.4 LTS, x64 installation • Devstack (full details in references section)
References 25
Reference Information • Heat • Heat main page • Heat developer documentation • Heat operations documentation • Heat github repository • Heat templates • Ironic • Ironic developer documentation • Ironic github repository • Ironic Project Technical Lead video presentation • Other • OpenStack project definitions • This presentation content – Email me for an invite to my public box folder