Ceilometer API - Enhancements of blueprint from D3
API in horizon for ceilometer
- Class wrappers of each Ceilometer entity
- Function wrappers for ceilometer queries
- High level wrappers for important table statistics and time series data, for Resources and Resource Aggregates (containing multiple resources)
- Optimization of high level wrappers:
1. Multithreading ( will get eventually replaced by Ceilometer API optimizations below )
2. Implementing Group-by ( https:/
3. Removing the constraint, that there have to be only one meter per statistic request. (https:/
- there will have to be probably a separate Group By for sample api (should be implicitly part of 3)
- there will probably have to be a Group By by metadata, if meter name will be stored in metadata (https:/
4. Ordering and limit of statistics, eg. top5 cpu consumers (https:/
Blueprint information
- Status:
- Complete
- Approver:
- David Lyle
- Priority:
- Medium
- Drafter:
- Ladislav Smola
- Direction:
- Needs approval
- Assignee:
- Ladislav Smola
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Blocked
- Milestone target:
- None
- Started by
- Ladislav Smola
- Completed by
- David Lyle
Related branches
Related bugs
| Bug #1226479: Abstraction of Ceilometer meters information | Fix Released |
| Bug #1226482: Support decorators in Ceilometer API methods | Invalid |
Sprints
Whiteboard
[2014-01-12 david-lyle] moving to i-3 as not started yet
[2014-02-03 | david-lyle] moving out of icehouse
Gerrit topic: https:/
Addressed by: https:/
Introduce safer access to resource meters
BLOCKED: for truly leveraging the GroupBy, we need complex queries for statistics, so we can query arbitrary groups of resources. That is now blocked by Timeseries as a Service in Ceilometer.
Work Items
Work items:
Multi-threading: DONE
Implementing group by, removing multi-threading: TODO
Implementing sample-api: TODO
Implementing ordering and limit: TODO
Dependency tree
* Blueprints in grey have been implemented.
