Structured and qualified notifications

Registered by Julien Danjou on 2013-09-04

Notifications API in Oslo is currently very generic and doesn't many structuring fields on the payload sent.
That doesn't help engine that would like to store, index and analyzes the event notifications.

Adding more documented fields that should/mut be present in notifiations could help a lot in this regard.

Blueprint information

Status:
Started
Approver:
Julien Danjou
Priority:
Medium
Drafter:
Julien Danjou
Direction:
Needs approval
Assignee:
Julien Danjou
Definition:
Approved
Series goal:
None
Implementation:
Needs Code Review
Milestone target:
None
Started by
Julien Danjou on 2014-01-13

Related branches

Sprints

Whiteboard

Definitely support adding an API for declaring notification schemas. Assuming it's icehouse-2 material at this point -- @markmc

+1 for adding an API as first step. Definitely do not like the idea of defining schema in code. Schema should be defined in a data file and enforced by code. See comments I added to the bottom of the spec. We should leave room for specs like CADF to easily fit into this mechanism. -Sandy

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

Addressed by: https://review.openstack.org/66566
    notify: add schema validation system

Addressed by: https://review.openstack.org/71032
    notify: add schema validation system

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.