Bug 1346366

Summary:	Expose parameter for enabling AODH-Event alarms
Product:	Red Hat OpenStack	Reporter:	Yurii Prokulevych <yprokule>
Component:	openstack-tripleo-heat-templates	Assignee:	Pradeep Kilambi <pkilambi>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0 (Mitaka)	CC:	dbecker, jcoufal, jdanjou, jruzicka, mburns, morazi, pkilambi, rhel-osp-director-maint, srevivo, yprokule
Target Milestone:	Upstream M3	Keywords:	Triaged
Target Release:	11.0 (Ocata)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-6.0.0-0.20170130212245.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-17 19:31:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yurii Prokulevych 2016-06-14 15:48:57 UTC

Description of problem:
-----------------------
Enabling events-alarm-evaluator is a bit tricky.
It would be great to have a parameter that if enabled configures all the parts.

The main parts are:
 - store_events enabled in ceilometer.conf
 - Event evaluator binds to queue (default alarm.all)
 - events are dispatched to AODH's evaluator and to Ceilometer's storage backend.

---
Yurii

Comment 2 Julien Danjou 2016-12-09 14:31:27 UTC

- Store_events has been removed and is automatically enabled if events pipeline is not empty
- Event evaluator binds to queue (default alarm.all) -> I think this is the default right?
- events are dispatched to AODH's evaluator and to Ceilometer's storage backend. -> so we can change the default to do that, *however*, if we do it by default and Aodh is not there running, RabbitMQ will explode. So I am not sure it's a good idea.

Hint? Idea? Is this enough Yurii?

Comment 3 Yurii Prokulevych 2016-12-09 14:49:14 UTC

Hi Julien,

So the original idea for the bz is to have a flag exposed to operator, which when enabled - configures all the aforementioned pieces.

Looks it has to be assigned for another component - director/t-h-t/...

Prad, since U are assignee on the upstream bz, could U please update the component?

Comment 4 Pradeep Kilambi 2016-12-09 16:48:40 UTC

I think last jd and i discussed this, We wanted all of this to happen in aodh/ceilometer itself, without any tweaks in tripleo. From what jd said above in comment#2 looks like its already taken care of in Aodh and Ceilometer?

Comment 5 Julien Danjou 2016-12-12 13:15:17 UTC

The only thing that cannot be done automatically by Ceilometer upstream is "Event evaluator binds to queue (default alarm.all)"

This should only be done if Aodh is enabled, by since Aodh is just a consumer of what Ceilometer might produce, there's no way to detect that.

So this should be enabled by TripleO when it sees that both Ceilometer and Aodh are configured together.

How does that sound Prad?

Comment 6 Pradeep Kilambi 2016-12-12 15:42:07 UTC

(In reply to Julien Danjou from comment #5)
> The only thing that cannot be done automatically by Ceilometer upstream is
> "Event evaluator binds to queue (default alarm.all)"
> 
> This should only be done if Aodh is enabled, by since Aodh is just a
> consumer of what Ceilometer might produce, there's no way to detect that.
> 
> So this should be enabled by TripleO when it sees that both Ceilometer and
> Aodh are configured together.
> 
> How does that sound Prad?

sure we can do that in puppet. We always configure aodh, so we can set the event_alarm_topic.

Comment 9 errata-xmlrpc 2017-05-17 19:31:06 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:1245