Versioned notification api (partial)
Versioned notification API
Notification interface of nova is not well defined and 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 nova sends.
Nova 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 nova notifications is really
hard.
Blueprint information
- Status:
- Complete
- Approver:
- John Garbutt
- Priority:
- Medium
- Drafter:
- Balazs Gibizer
- Direction:
- Approved
- Assignee:
- Balazs Gibizer
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Implemented
- Milestone target:
-
mitaka-3
- Started by
- Balazs Gibizer
- Completed by
- John Garbutt
Related branches
Related bugs
Sprints
Whiteboard
Spec: https:/
Gerrit topic: https:/
Addressed by: https:/
Versioned notification API
Addressed by: https:/
[WIP] Add versioned notifications for keypair API
Gerrit topic: https:/
Addressed by: https:/
Add service status notification
Addressed by: https:/
Add infra for versioned notifications
Addressed by: https:/
Make emitting versioned notifications configurable
Addressed by: https:/
Adds json sample for the versioned notifications
Gerrit topic: https:/
Addressed by: https:/
doc: add devref about versioned notifications
Addressed by: https:/
Use extra_data_func to get fingerprints of objects
Addressed by: https:/
Generate doc for versioned notifications
Addressed by: https:/
doc:Ask reviews to reject new legacy notifications
Addressed by: https:/
Forbid new legacy notification event_type
Addressed by: https:/
DNM: try to wrap mock.patch and mock.patch.object
Work Items
Dependency tree
* Blueprints in grey have been implemented.
