[openstack-dev] [Vitrage] [Aodh] Vitrage – Aodh Integration
Weyl, Alexey (Nokia - IL)
alexey.weyl at nokia.com
Thu Dec 8 12:46:49 UTC 2016
Hi Julien,
Thank you for your response.
> > We are starting to work on the following BP proposal:
> > https://review.openstack.org/#/c/408060/
> >
> > In this regard, I have two questions:
> > 1. What should this new alarm be called?
>
> Ah naming things, the biggest problem in CS. Well I'd pick "manual" as
> a name to indicate that nothing is done by Aodh evaluator. Thoughts?
>From Vitrages' point of view "manual" the action is not manual because it is all done automatically.
How about "generic"? "custom"? "external"?
> > 2. As I'm new in Aodh, do you have any pointers or suggestions about
> where to start?
>
> Not really, though deploying it and using it is probably a good start.
> The spec you started is a good idea to lay out your thoughts and will
> help us understand and point any issue we may have missed.
I have already used ceilometer and aodh in the past.
I am trying to understand where exactly in Aodh code the new alarm should be because it is not part of the evaluator (as other alarms are).
I am waiting for your thoughts on the spec.
Thanks,
Alexey Weyl
> -----Original Message-----
> From: Julien Danjou [mailto:julien at danjou.info]
> Sent: Thursday, December 08, 2016 2:27 PM
> To: Weyl, Alexey (Nokia - IL)
> Cc: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Vitrage] [Aodh] Vitrage – Aodh
> Integration
>
> On Wed, Dec 07 2016, Weyl, Alexey (Nokia - IL) wrote:
>
> Hi Alexey,
>
> > We are starting to work on the following BP proposal:
> > https://review.openstack.org/#/c/408060/
> >
> > In this regard, I have two questions:
> > 1. What should this new alarm be called?
>
> Ah naming things, the biggest problem in CS. Well I'd pick "manual" as
> a name to indicate that nothing is done by Aodh evaluator. Thoughts?
>
> > 2. As I'm new in Aodh, do you have any pointers or suggestions about
> where to start?
>
> Not really, though deploying it and using it is probably a good start.
> The spec you started is a good idea to lay out your thoughts and will
> help us understand and point any issue we may have missed.
>
> I'll review your spec ASAP.
>
> Cheers,
> --
> Julien Danjou
> /* Free Software hacker
> https://julien.danjou.info */
More information about the OpenStack-dev
mailing list