Difference between revisions of "Ceilometer-batch-consumption"
| Line 20: | Line 20: | ||
The intention is to create the ability for all message collection pipelines in ceilometer to use batching if so desired. The initial implementation will focus on notification collection. | The intention is to create the ability for all message collection pipelines in ceilometer to use batching if so desired. The initial implementation will focus on notification collection. | ||
| − | |||
File:Batch notification.jpg|Proposed Data Flow | File:Batch notification.jpg|Proposed Data Flow | ||
| − | |||
== Implementation == | == Implementation == | ||
Revision as of 21:08, 10 January 2014
- Launchpad Entry: CeilometerSpec:use-bulk-notification
- Created: 09 Jan 2014
- Contributors: John Herndon <john.herndon@hp.com>
Contents
Summary
Currently, ceilometer handles notifications one at a time. Individual events are inserted into the storage back-end, individual notifications are handled as meters, etc. In many cases, it is more efficient to handle notifications many at a time, in a batch. This blueprint proposes a way to do that.
Release Note
Rationale
User stories
Assumptions
- This feature will be configurable. If an operator does not wish to use batching, it will remain off.
- Dependent on https://review.openstack.org/#/c/57457/
Design
The intention is to create the ability for all message collection pipelines in ceilometer to use batching if so desired. The initial implementation will focus on notification collection.
File:Batch notification.jpg|Proposed Data Flow
Implementation
UI Changes
Code Changes
Migration
Include:
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
Test/Demo Plan
This need not be added or completed until the specification is nearing beta.
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
