Open Stack

On Wed, Dec 02 2015, ROSENSWEIG, ELISHA (ELISHA) wrote:

> Regarding the second point: Say we have 30 different types of alarms we might
> want to raise on an OpenStack instance (VM). What I understand from your
> explanation is that when we create a new instance, we need to create 30 new
> alarms in Aodh that can be triggered some time in the future. If we have 100
> instances, we will effectively have 3,000 alarms created in Aodh, and so on
> with more instances.

Not necessarily. You can create one alarm that has conditions large
enough to match e.g. all your VMs, and an alarm action that can be
generic enough so that it will do the right thing for each VM.

The alarm system provided by Aodh is really a simple event -> trigger
system in this area. How precise or large is your event really depends
on the granularity that your trigger (which is usually a Web hook) can
handle.

> A different approach might be to create a new alarm in Aodh on-the-fly.
> However, we are under the impression that the creation time can be up to one
> minute, which will cause a large delay. Is there any way to shorten this?

Creation time of an alarm of one minute? That's not normal. It should
consist of just a record in the database so it should be pretty fast.

-- 
Julien Danjou
// Free Software hacker
// https://julien.danjou.info
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151202/c4ff1e97/attachment.pgp>