Discuss adding notification data with service teams
Best performance will come from indexing purely from notifications. Currently there's information that we can only get from the API (glance metadefs are a good and tricky example, but nova instance notifications don't necessarily have all we would like).
There's also a larger conversation about potential crossover with e.g. log data, ceilometer - the idea of using log data has been floated. That should be a separate discussion with a larger focus - this blueprint is intended to specifically target the existing implementation.
Identify where we're missing things, and discuss with service teams whether what we want is possible and whether they'd be ok us adding it. If there is nothing to do for a service, all the better.
Current services with planned or existing support:
* glance
* nova
* designate
* swift
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- High
- Drafter:
- Steve McLellan
- Direction:
- Needs approval
- Assignee:
- Travis Tripp
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Informational
- Milestone target:
- None
- Started by
- Travis Tripp
- Completed by
- Travis Tripp
Related branches
Related bugs
Sprints
Whiteboard
Travis - We need to keep notifications in synch with the API results, so part of this discussion needs to include determining whether or not trying to always go through notifications is a larger maintenance burden with larger opportunity for things to get out of sync.
Added etherpad with the differences between notifications and apis at https:/
yuntongjin - Nova is planning to use Versioned notification API, which make it easier to track notification change.
https:/
NOTE:
TravT / sjmc7 discussed with Nova team
sjmc7 / briancline discussed with swift
lakshmiS discussed with ceilometer
