Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Heat : Think templates and automation. You have three web servers in front of a database cluster. Your template specifies that there should always be three web servers. Someone else logs into the cloud and deletes one of the web servers. Heat will deploy another web server automatically (if you configured everything correctly.) Heat will also automate deployment of certain stacks if there are templates out there. Such as it will auto deploy a stack for Word Press if you wanted.

Ceilometer : Provides a type of resource monitoring and alarms for configured triggers. If you add this you could use it to generate data about usage for tenants and have data to create a pricing model or charge back. You could also use parts of this with heat for Auto Scaling. You have three web servers, you create a trigger in Ceilometer to let you know when those three servers hit 90% CPU, when that happens trigger an alarm to create another instance. Now you have four web servers instead of three, you could also scale back down when everything drops below 90%.

Trove : Database as a service. Not as familiar with it but it's adding another tool set to help end users configure Databases without having to know Linux Administrator or Server level configurations.

All of these tools are additions to OpenStack to keep it competitive with services such as AWS. You'll notice a large amount of overlap of functions between AWS and OpenStack. It's not always 1:1 and sometimes OpenStack is ahead of AWS with what it is doing, but you'll usually see some type of correlation.