declarative notification handling
The existing implementation of notification handling has various limitations.
* There is no way to selectively listen to specific event topics of interest.
* Capturing notifications of interest should not require code changes.
* Adding new event exchanges involves same routine code changes. Too much code duplication.
* Requires more insight into the code base than needed
* more elegant exchange control
This proposal takes a more declarative approach in addressing these concerns.
Blueprint information
- Status:
- Complete
- Approver:
- Chris Dent
- Priority:
- High
- Drafter:
- Pradeep Kilambi
- Direction:
- Approved
- Assignee:
- Pradeep Kilambi
- Definition:
- Approved
- Series goal:
- Accepted for liberty
- Implementation:
-
Implemented
- Milestone target:
-
5.0.0
- Started by
- Pradeep Kilambi
- Completed by
- Pradeep Kilambi
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Declarative notification handling
Addressed by: https:/
Declarative meters support
Addressed by: https:/
Convert identity, sahara and image to meters yaml
Addressed by: https:/
Enable entry points for new declarative meters
Addressed by: https:/
Delete old notification handlers
Gerrit topic: https:/
Addressed by: https:/
Convert instance, bandwidth and SwiftMiddleware meters
Addressed by: https:/
support multiple-meter payloads
Gerrit topic: https:/
Addressed by: https:/
add test to validate jsonpath
Addressed by: https:/
Add support to compute cpu meters in yaml
Addressed by: https:/
full multi-meter support
Addressed by: https:/
Move profiler meters to yaml
Gerrit topic: https:/
Addressed by: https:/
support custom metadata
Addressed by: https:/
support custom timestamp
Addressed by: https:/
Add cpu meters to yaml
Addressed by: https:/
fix metadata for compute cpu notifications
Work Items
Dependency tree
* Blueprints in grey have been implemented.
