Agenda

1. 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 speaker About Rackspace Heat Background Heat Architecture Heat Operations Heat Demo Heat Group Exercise 1 1

2. About the Speaker 2

3. OpenStack Heat 101 Capabilities, Use Case and Demo Presented to Atlanta OpenStack Meetup March 2014

4. About the Speaker Grant Park East Cobb Georgia Native Boston Key West Canton • Lots of hats… • Husband • Father • Veteran • Farmer • Architect • Lots of interests… • Music • Movies • Politics • Gun Collecting • Comedy Startup Co-Founder 2000-2004 Freelance 1996-2000 Mirantis Puppet / Fuel 2013 US Naval Intelligence 1992-1996 Dell Ruby / Crowbar 2004-2013 Rackspace Chef / RPC 2013-2014

5. About Rackspace 5

6. 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

7. OpenStack History John Dickinson Chris Kemp PUBLIC CLOUD OpenStack Mission: “To enable any organization, regardless of size, to create and offer cloud computing services running on standardized hardware.” PRIVATE CLOUD

8. 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

9. Heat Background 9

10. 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.“

11. 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

12. 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

13. OpenStack Project Lifecycle I made mention of core projects, what other types are there? Open Discussion – request assistance from OpenStack contributors Ironic project as an example: September 2012 San Diego Folsom / Grizzly Summit October 2013 Hong Kong Havana / Icehouse Summit April 2013 Portland Grizzly / Havana Summit May 2014 Atlanta Icehouse / Juno Summit Became a recognized “incubated” project Became a stand alone project Started as an experimental “bare metal” driver for Nova Became a recognized stand alone “related” project Slated to become a “core” project, i.e. BMaaS Bare Metal as a Service

14. Heat Architecture 14

15. 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.

16. Heat Architecture (Quick Overview) • Concepts to cover • Stateless (API) • Stateful • DB • MQ • Interfaces • Web-UI • CLI • API

17. Heat Operations 17

18. Heat is HOT The power of Heat is HOT (Heat Orchestration Templates) *

19. Heat Demo 19

20. 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)

21. References 21

22. 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