This session will include the following subject(s):
Time series data manipulation in nosql stores:
Ceilometer currently supports multiple storage drivers (mongodb, sqlalchemy, hbase) behind a well-defined abstraction.
The purpose of this design session is to discuss how well suited the existing nosql stores are to the efficient manipulation of time-series data.
The questions to be decided would include:
* whether we could optimize/improve our existing schemas in this regard
* whether we should consider a storage driver based on Cassandra in order to take advantage of it's well-known suitability for TSD
(Session proposed by Eoghan Glynn)
The dotted line between metering and metric/alarms:
There is clear commonality in the data acquisition & transformation layers for gathering metering and metric data.
However the further we venture through the pipeline, there are also operation concerns around over-sharing of common infrastructure in the transport and storage layers.
We need to tie to down exactly where we see the dotted line between the handling of metering and metric data, deciding whether:
* a common conduit in the form of AMQP should be used for publication (for example given that during a brownout in the RPC layer, we would need a timely metric flow more than ever)
* a common storage layer should be used for persistence (for example given that data retention requirements may differ significantly)
* a common API layer should provide aggregation (for example given that certain aggregations such as percentile may make far more sense for metric rather than metering data)