Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Heat return the status of stack creation on its own independent of ceilometer. If ceilometer is down you would not get any of the usage statistics [for any service - nova, cinder, heat etc.], so if you are not bothered about getting statistics of resource usage - then not to worry.

However, if your Heat template also creates any alarms and scaling policies then obviously ceilometer has to be operations in order to create those resources via heat.

regs, nd

Heat return the status of stack creation on its own independent of ceilometer. If ceilometer is down you would not get any of the usage statistics [for any service - nova, cinder, heat etc.], so if you are not bothered about getting statistics of resource usage - then not to worry.

However, if your Heat template also creates any alarms and scaling policies then obviously ceilometer has to be operations in order to create those resources via heat.

regs, nd

Response to your comment: Hi Heather,

As far as Heat orchestration and Ceilometer are concerned - these are completely independent services and can operate without each other - unless you want to use Ceilometer alarms and Scaleup policy [typically for creating auto scaling template] So, if you want to launch stack which is not using resources like alarm and scaleup policy - then you can very well go ahead and launch stacks without Ceilometer. The stack will complete successfully as well as you will see the status of stack completion. No issues. I have checked this also in my environment as a double check.

regs, nd