Unleash Your Potential - Namagunga Girls Coding Club
Openstack heat & How Autoscaling works
1. Openstack Heat & How Autoscaling works
@Openstack chennai meetup Aug 2015
Jayaprakash
Technical Lead, Product Development
jayaprakash.r@cloudenablers.com
Beny Raja
Technical Lead, DevOps
benyraja.j@cloudenablers.com
2. Overview
●Heat is the orchestration component of Openstack.
Template-driven engine that allows us to describe and
automate the deployment of infrastructure &
application
●Extended capabilities such as Nested stacks,
Resource Groups, Auto scaling, Software deployment
using configuration management tools like puppet
3. Services
●Heat - CLI which communicates with heat-api
●Heat-api - REST based service which sends api
requests to heat-engine via RPC
●Heat-engine - Orchestrates openstack resources
●Heat-api-cfn - REST based service which sends api
requests to heat-engine via RPC
7. Develop your own Resource Plugins
●Plugin Life cycle –
Create,Update,Suspend,Delete,Resume
●Registering resource plugin name –
OS::Nova::Workload
●Properties & Attributes
●Handler Methods – handle_create, handle_update,
handle_delete...
●Configure heat to register new plugins and restart
heat-engine service
Reference:
http://docs.openstack.org/developer/heat/pluginguide.html
9. Autoscaling
●To maintain application availability and allows you to
scale the capacity up or down automatically
according to conditions you define
●Automatically increase the number of instances
during demand spikes to maintain performance
●Heat & Ceilometer are the components used to
implement Autoscaling in Openstack