Versioned notification
the current notifications define a very inconsistent interface.
There is no easy way to see from the notification consumer point of view what is the format
and the content of the notification keystone sends.
developers can add new notifications to the system without specifying
the format and the content of the notification.
Moreover developers can change existing notifications without considering
backward compatibility towards the notification consumers.
Due to this situation maintaining a consumer for keystone notifications is really
hard.
This kind of work is being worked in nova:
https:/
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- yuntongjin
- Direction:
- Needs approval
- Assignee:
- yuntongjin
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Lance Bragstad
Related branches
Related bugs
Sprints
Whiteboard
(lbragstad) 19-02-13: Keystone supports the pycadf notification format, which is available here [0]. I'm marking this as obsolete for now, but if you'd like to continue the discussion, please propose a specification to the openstack/
[0] https:/
[1] http://
