What is the drawbacks of listening to UDP/RPC publication of ceilometer

asked 2014-12-18 16:10:30 -0600

dsrini gravatar image

updated 2014-12-19 18:29:24 -0600

smaffulli gravatar image

Is Heat the only way to autoscale? What are the pros and cons of doing the below, please advice.

  1. Listen to UDP publications from Ceilometer > This should give the heartbeat of the activities in the system
  2. Setup ceilometer to trigger when to autoscale and downscale
  3. Initiate autoscale/downscale through REST APIs to neutron/nova.

What is the drawbacks of listening to UDP/RPC publication of cielometer as above?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2014-12-23 19:00:45 -0600

Darkinvader gravatar image

The question is why are you trying to do this without using heat and autoscale? The main drawback is that you are solving problem that is already solved by Heat and Ceilometer Alarm.

To be fair you do not have to use Heat to autoscale. You can write entire separated small program that just check how busy your pool of VMs is and send API to create new instance when needed. However, this would be poor's man solution. Heat is working it in the elegant way by creating Ceilometer alarm that you can confugure to how sensitive it should be, it works well, I tested it and it is not that difficult.

go pro, go heat+autoscale

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-12-18 16:10:30 -0600

Seen: 550 times

Last updated: Dec 19 '14