Gnocchi/Ceilometer Integration Task-List (Kilo-3)

	A	B	C	D	E	F
1		Details / sub-tasks	Assignee	In progress?	Target	Progress
2	Data migration for existing metering stores	mine the meters/resources collections and map to analogous data in gnocchi, discarding unused metadata (perhaps use proposed synchronization API?)	?	No	kilo-3
3		mine the samples event_type metadata to reconsturct events+traits if not already stored, in order to emulate the resource state timeline formerly persisted in the resource_metadata
4		document guidance for running gnocchi in parallel with classic datastore, before completely switching over	fabiog	No
5
6	Ceilometer alarming rebased on the gnocchi get measures API	restrict alarm constraints to strongly typed resource attributes	sileht	Yes	kilo-3
7		redefine alarm periods to be wall-clock clamped	idegtiarov	No
8		restrict alarm periods to the granularities exposed in the ArchivePolicy of the corresponding metric	_elena_	Yes	kilo-3	https://review.openstack.org/#/c/159837/
9		allow new aggregate functions to be used in alarms (stdev etc.)	sileht			I think sileht is working on that too.
10		create heat resources for this alarms	sileht	Yes	kilo-3	There are patches on Heat waiting to be merged
11
12	Ceilometer v3 API to address mismatches/ impedence with v2 statistics/samples API	no arbitrary periodization support (defined up front in the ArchivePolicy)	?	No	kilo-3	I don't think this is an item to do. It's just a documentation issue at worst.
13		periods clamped to wall-clock boundaries instead of being anchored on NOW				I don't think this is an item to do. It's just a documentation issue at worst.
14		no groupby support				I don't think this is an item to do. It's just a documentation issue at worst.
15		incomplete aggregate function support (no selectable cardinality aggregate)			lemming-*
16		no arbitrary metadata constraints				I don't think this is an item to do. It's just a documentation issue at worst.
17
18	Ceilometer/gnocchi dispatcher improvements	allow ArchivePolicy used for individual metric types to be configurable (e.g. map cpu_util to "high", disk.write.bytes to "low")	prad	Yes	kilo-3	https://review.openstack.org/#/c/156617/
19		allow gnocchi storage driver to be delpoyed in-process in the collector			lemming-*
20
21	Extend python-ceilometerclient to support v3 API and/or provide python-gnocchiclient	allow transitional queries to span both classic and gnocchi datastores?	jd	Yes	kilo-3	jd is writing patch in python-openstacksdk and some got merged
22
23	Performance profiling / storage footprint measurement to demosntrate benefits of gnocchi	publish comparison of classic ceilometer versus gnocchi metric ingestion and query performance (for a subset of storage drivers, e.g. mongodb versus carbonara+swift & mongodb versus influx)	sileht?	No	RC1
24		publish comparison of storage footprint classic ceilometer (e.g. mongodb) versus gnocchi for a given cloud size	jd
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100