notification agent coordination

Registered by gordon chung

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.

Blueprint information

Status:
Complete
Approver:
Eoghan Glynn
Priority:
Medium
Drafter:
gordon chung
Direction:
Approved
Assignee:
gordon chung
Definition:
Approved
Series goal:
Accepted for kilo
Implementation:
Implemented
Milestone target:
milestone icon 2015.1.0
Started by
Eoghan Glynn
Completed by
Eoghan Glynn

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:notification-coordination,n,z

Addressed by: https://review.openstack.org/133287
    Notification Agent Coordination

Gerrit topic: https://review.openstack.org/#q,topic:bp/notification-coordination,n,z

Addressed by: https://review.openstack.org/135414
    notification coordination WIP

Marking as blocked pending the corresponding specs patch landing:

    https://review.openstack.org/#/c/133287/5/specs/kilo/notification-coordiation.rst

Addressed by: https://review.openstack.org/139203
    ensure unique pipeline names

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.