Configurable Notifications Routing

Registered by Monsyne Dragon on 2013-02-12

Openstack projects produce a wide variety of notification messages describing events occurring inside the system. These may be used for usage billing, performance monitoring, and other integration tasks. This blueprint proposes an optional notification driver that can route notification events to other notification drivers based on the notification's event_type, using a configuration specified in a json config file. This will allow some events to be delivered via a more robust delivery mechanism like AMQP that has guaranteed delivery, while others are delivered via lighter weight methods that are faster and have a higher throughput, but may not have such guarantees (which may not be needed for the application they are being used for), and still other notifications, not needed for a given install, may be dropped altogether.

Blueprint information

Status:
Complete
Approver:
Mark McLoughlin
Priority:
Low
Drafter:
Monsyne Dragon
Direction:
Approved
Assignee:
Sandy Walsh
Definition:
Discussion
Series goal:
Accepted for icehouse
Implementation:
Implemented
Milestone target:
milestone icon 1.3.0
Started by
Mark McLoughlin on 2013-12-17
Completed by
Mark McLoughlin on 2014-01-23

Related branches

Sprints

Whiteboard

Ceilometer has a similar idea for our publisher pipeline. I wonder if we could share some of the underlying code? -- dhellmann

Monsyne - any updates on this proposal? -- @markmc

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

Addressed by: https://review.openstack.org/60018
    Routing notifier

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.