Bug 1162432

Summary:	[RFE][ceilometer]: notification agent coordination
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-ceilometer	Assignee:	Eoghan Glynn <eglynn>
Status:	CLOSED ERRATA	QA Contact:	Yurii Prokulevych <yprokule>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	jruzicka, markmc, pbrady, rrosa, yeylon
Target Milestone:	Upstream M1	Keywords:	FutureFeature, OtherQA, Triaged
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/ceilometer/+spec/notification-coordination
Whiteboard:	upstream_milestone_kilo-1 upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-ceilometer-2015.1.0-2.el7ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:15:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-11-11 05:04:18 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/notification-coordination.

Description:

Currently, the notification agent can function in active/active HA where each
notification agent grabs notifications from the message queue in a FIFO type
rotation (it checks for message(s), grabs message(s)). The issue that arises is
that if we want to implement a pipeline to process events, we cannot guarantee
what event each agent worker will get and because of that, we cannot enable
transformers which aggregate/collate some relationship across similar events.

This also fixes an existing bug where if multiple notification agents are
enabled, the pipeline transformers may not work as expected because it will
only act on the samples it sees on current worker.


Specification URL (additional information):

None

Comment 6 Yurii Prokulevych 2015-06-26 13:45:34 UTC

Verified according test plan.

Comment 8 errata-xmlrpc 2015-08-05 13:15:38 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-2015:1548