Versioned notification
the current neutron 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 neutron sends.
Neutron 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 neutron 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
- Armando Migliaccio
Related branches
Related bugs
Sprints
Whiteboard
You are not supposed to create blueprints, and bypass the RFE submission process as defined in [1].
[1] http://
---------------
