Bug 1041998

Summary:	[RFE][horizon]: Ceilometer API - Enhancements of blueprint from D3
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	python-django-horizon	Assignee:	Matthias Runge <mrunge>
Status:	CLOSED NOTABUG	QA Contact:	Shai Revivo <srevivo>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aortega, athomas, markmc, mrunge, nbarcet, srevivo
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/horizon/+spec/ceilometer-api-enhancements
Whiteboard:	upstream_milestone_next upstream_status_blocked upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-14 08:46:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 20:30:20 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/ceilometer-api-enhancements.

Description:

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://blueprints.launchpad.net/ceilometer/+spec/api-group-by )
3. Removing the constraint, that there have to be only one meter per statistic request. (https://blueprints.launchpad.net/ceilometer/+spec/sample-api)
- 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://wiki.openstack.org/wiki/Ceilometer/blueprints/multi-dimensions, should be implicitly part of 3)
4. Ordering and limit of statistics, eg. top5 cpu consumers (https://blueprints.launchpad.net/ceilometer/+spec/statistics-order-by-and-limit-for-grouped-query)


Specification URL (additional information):

None

Comment 5 Matthias Runge 2016-06-14 08:46:29 UTC

This looks dead upstream.