]
Sent: Tuesday, May 03, 2016 6:05 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [vitrage] [aodh] Error when creating 2 event
alarms with the same name
Alarm name unique constraint is only applied to each project, I don't remember
the original
to:jul...@danjou.info]
> Sent: Tuesday, May 03, 2016 6:03 PM
> To: Weyl, Alexey (Nokia - IL)
> Cc: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [vitrage] [aodh] Error when creating 2
> event alarms with the same name
>
> On Tue, May 03 2016, Weyl, Alexey (Nokia - IL)
Alarm name unique constraint is only applied to each project, I don't
remember the original cause, but in our customer's environment, alarm will
be showed in the portal, with their name, no uuid, because user will be
confused about such a random like string, then if alarm name can be
duplicated,
On Tue, May 03 2016, Weyl, Alexey (Nokia - IL) wrote:
> Do you think it is possible to drop the uniqueness of the alarm name in Aodh
> (for the Vitrage use cases that we talked about in the design session)?
Should be doable yeah, it's really just a (badly written) check in the
API.
Shoot us a
Hi,
First of all, I wanted to thank again to all the participants in the fruitful
Aodh-Vitrage design session in Austin :)
I wanted to show in this email, the problem that we have when creating 2 event
alarms with the same name.
Here is what I got in the command line:
