Bug 1042322

Summary: [RFE][ceilometer]: Add "aggregate" and "rolling_up" features
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/ceilometer/+spec/aggregation-and-rolling-up
Whiteboard: upstream_milestone_none upstream_status_started upstream_definition_superseded
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:13:46 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 21:44:56 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/aggregation-and-rolling-up.

Description:

This is an umbrella blueprint for such features as:
 - Aggregation data
 - Queries precalculations (including Big Data processing)  (later)
 - Rolling up sample data
All of these features have one thing in common: there should be some 'manager' that will start corresponding process (e.g. 'aggregation' or 'archivation').  Besides, I believe that the same logic and even the code may be reused for implementing all the features. E.g. Rolling up may be processed using some Big Data service (2 and 3 may be combined), aggregation is the same as rolling up but without data removing and so on. So all of these features should be very flexible and we need to work out the pluggable architecture that may be easy extensible.

Example for Mongo: https://etherpad.openstack.org/p/ceilometer-aggregation

Specification URL (additional information):

None