OpenStack - User contributions [en]

Telemetry/RoadMap

2018-01-25T13:51:14Z

Gordon chung: /* Ceilometer (data collection) */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active

=== All Projects ===
* service status interface
** raise details on health, message processing rate, etc...

=== Aodh (alarming) ===
* [https://bugs.launchpad.net/aodh/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* alarm CRUD events
* send aodh CRUD events to panko
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* [https://bugs.launchpad.net/ceilometer/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* rolling upgrades test gate
* rally tests

=== Panko (event storage) ===
* [https://bugs.launchpad.net/panko/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* tempest tests

=== Gnocchi (metric storage) ===
* NOTE: Gnocchi has moved outside of OpenStack scope. It is developed outside of OpenStack but will remain compatible.
* Issues tracked at [https://github.com/gnocchixyz/gnocchi/issues gnocchi github]

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry

2017-12-06T18:23:58Z

Gordon chung: /* Gnocchi */

= OpenStack Telemetry =

== Project Mission ==
To reliably collect data on the utilization of the physical and virtual resources comprising deployed clouds, persist these data for subsequent retrieval and analysis, and trigger actions when defined criteria are met.

== Services ==
The telemetry requirements of an OpenStack environment are vast and varied, they include use cases such as metering, monitoring, and alarming to name a few. The scope of these uses cases are diverse and beyond the scope of a single project and team. Currently, the telemetry project provides a set of functionality split across multiple projects; each project designed to provide a discrete service in the telemetry space.

=== Managed ===
The current set of projects are managed by the telemetry team are:
* [https://github.com/openstack/aodh Aodh] - an alarming service
* [https://github.com/openstack/ceilometer Ceilometer] - a data collection service
* [https://github.com/gnocchixyz/gnocchi Gnocchi] - a time-series database and resource indexing service
* [https://github.com/openstack/panko Panko] - an event, metadata indexing service

{| border="1" cellpadding="2" cellspacing="0"
| Specs
| https://github.com/openstack/ceilometer-specs
|-
| Admin doc
| http://docs.openstack.org/admin-guide-cloud/telemetry.html
|-
| Meetings
| https://wiki.openstack.org/wiki/Meetings/Telemetry
|}

Currently, a common spec repo and meeting time are shared between all managed projects

==== Aodh ====
* team lead - tbd
Aodh's goal is to enable the ability to trigger actions based on defined rules against sample or event data collected by Ceilometer

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/aodh
|-
| Bug tracker
| https://bugs.launchpad.net/aodh
|-
| Docs
| https://docs.openstack.org/aodh/latest/
|-
| Tarballs
| http://tarballs.openstack.org/aodh/
|}

==== Ceilometer ====
* team lead - Gordon Chung (gordc)
Ceilometer's goal is to efficiently collect, normalise and transform data produced by OpenStack services. The data it collects is intended to be used to create different views and help solve various telemetry use cases. Aodh and Gnocchi are two examples of services extending Ceilometer data.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/ceilometer
|-
| Bug tracker
| https://bugs.launchpad.net/ceilometer
|-
| Docs
| https://docs.openstack.org/ceilometer/latest/
|-
| Tarballs
| http://tarballs.openstack.org/ceilometer/
|}

==== Panko ====
* team lead - tbd
Panko is designed to provide a metadata indexing, event storage service which enables users to capture the state information of OpenStack resources at a given time. Its aim is to enable a scalable means of storing both short and long term data for use cases such as auditing and system debugging.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/panko
|-
| Bug tracker
| https://bugs.launchpad.net/panko
|-
| Docs
| https://docs.openstack.org/panko/latest/
|-
| Tarballs
| http://tarballs.openstack.org/panko/
|}

=== Externally Managed (Non-OpenStack) ===
==== Gnocchi ====

Gnocchi's goal is to provide a time-series resource indexing, metric storage service which enables users to capture OpenStack resources and the metrics associated with them. Using rolling aggregation set by user-defined archival policies, it's aim is to provide a scalable means of storing both short and long term data and provide a statistical view based on the input data (ie. Ceilometer)

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/gnocchixyz/gnocchi
|-
| Bug tracker
| https://github.com/gnocchixyz/gnocchi/issues
|-
| Docs
| http://gnocchi.xyz
|-
| Tarballs
| https://pypi.python.org/pypi/gnocchi
|}

=== Externally Managed ===
* [https://github.com/openstack/heat Heat] - Orchestration service which provides autoscaling capabilities using Ceilometer data.
* [https://github.com/openstack/horizon Horizon] - UI service which allows interaction with Aodh data.
* [https://github.com/stackforge/ceilometer-powervm PowerVM] - PowerVM pollster plugin. Owners: thorst and efried. IRC: #openstack-powervm
* [https://github.com/stackforge/cloudkitty CloudKitty] - OpenStack Rating as a Service component and usage reporting.
* [https://github.com/spilgames/ceilometer_graphite_publisher Graphite Publisher] - Ceilometer publisher to connect to Graphite.
* [https://github.com/openstack/watcher Watcher] - Resource optimization service.
* [http://icclab.github.io/cyclops Cyclops] - Rating-Charging-Billing Solution for Cloud providers.
* [https://github.com/gnocchixyz/collectd-gnocchi Collectd] - A Collectd writer plugin to publish telemetry to Gnocchi.

== Road Map ==
The future direction and plans of the project can be found [[Telemetry/RoadMap|here]]. Feel free to pick up a task if something interests you. Anyone is free to propose their own ideas in a patch as well.

== Contributing to Telemetry ==
The developer documentation can be found in each projects respective documentation page.

The telemetry project team hangs out on Freenode in the #openstack-telemetry channel, feel free to drop by and stay as long as you want. We use the [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Developers List] for our email discussions. If you want to make a post relevant to multiple projects in telemetry space,
please tag the subject with [telemetry]. If you have a post regarding a single project, please tag the subject with the appropriate tag: [aodh], [ceilometer], [gnocchi], or [panko].

The project team officially reserves a meeting slot but does not utilise it unless discussion items are raised to mailing list. see [[Meetings/Telemetry]].

[[Category:Telemetry]]

Telemetry

2017-12-06T18:23:38Z

Gordon chung: /* Ceilometer */

= OpenStack Telemetry =

== Project Mission ==
To reliably collect data on the utilization of the physical and virtual resources comprising deployed clouds, persist these data for subsequent retrieval and analysis, and trigger actions when defined criteria are met.

== Services ==
The telemetry requirements of an OpenStack environment are vast and varied, they include use cases such as metering, monitoring, and alarming to name a few. The scope of these uses cases are diverse and beyond the scope of a single project and team. Currently, the telemetry project provides a set of functionality split across multiple projects; each project designed to provide a discrete service in the telemetry space.

=== Managed ===
The current set of projects are managed by the telemetry team are:
* [https://github.com/openstack/aodh Aodh] - an alarming service
* [https://github.com/openstack/ceilometer Ceilometer] - a data collection service
* [https://github.com/gnocchixyz/gnocchi Gnocchi] - a time-series database and resource indexing service
* [https://github.com/openstack/panko Panko] - an event, metadata indexing service

{| border="1" cellpadding="2" cellspacing="0"
| Specs
| https://github.com/openstack/ceilometer-specs
|-
| Admin doc
| http://docs.openstack.org/admin-guide-cloud/telemetry.html
|-
| Meetings
| https://wiki.openstack.org/wiki/Meetings/Telemetry
|}

Currently, a common spec repo and meeting time are shared between all managed projects

==== Aodh ====
* team lead - tbd
Aodh's goal is to enable the ability to trigger actions based on defined rules against sample or event data collected by Ceilometer

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/aodh
|-
| Bug tracker
| https://bugs.launchpad.net/aodh
|-
| Docs
| https://docs.openstack.org/aodh/latest/
|-
| Tarballs
| http://tarballs.openstack.org/aodh/
|}

==== Ceilometer ====
* team lead - Gordon Chung (gordc)
Ceilometer's goal is to efficiently collect, normalise and transform data produced by OpenStack services. The data it collects is intended to be used to create different views and help solve various telemetry use cases. Aodh and Gnocchi are two examples of services extending Ceilometer data.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/ceilometer
|-
| Bug tracker
| https://bugs.launchpad.net/ceilometer
|-
| Docs
| https://docs.openstack.org/ceilometer/latest/
|-
| Tarballs
| http://tarballs.openstack.org/ceilometer/
|}

==== Panko ====
* team lead - tbd
Panko is designed to provide a metadata indexing, event storage service which enables users to capture the state information of OpenStack resources at a given time. Its aim is to enable a scalable means of storing both short and long term data for use cases such as auditing and system debugging.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/panko
|-
| Bug tracker
| https://bugs.launchpad.net/panko
|-
| Docs
| https://docs.openstack.org/panko/latest/
|-
| Tarballs
| http://tarballs.openstack.org/panko/
|}

=== Externally Managed (Non-OpenStack) ===
==== Gnocchi ====

Gnocchi's goal is to provide a time-series resource indexing, metric storage service which enables users to capture OpenStack resources and the metrics associated with them. Using rolling aggregation set by user-defined archival policies, it's aim is to provide a scalable means of storing both short and long term data and provide a statistical view based on the input data (ie. Ceilometer)

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/gnocchixyz/gnocchi
|-
| Bug tracker
| https://github.com/gnocchixyz/gnocchi/issues
|-
| Developer doc
| http://gnocchi.xyz
|-
| Tarballs
| https://pypi.python.org/pypi/gnocchi
|}

=== Externally Managed ===
* [https://github.com/openstack/heat Heat] - Orchestration service which provides autoscaling capabilities using Ceilometer data.
* [https://github.com/openstack/horizon Horizon] - UI service which allows interaction with Aodh data.
* [https://github.com/stackforge/ceilometer-powervm PowerVM] - PowerVM pollster plugin. Owners: thorst and efried. IRC: #openstack-powervm
* [https://github.com/stackforge/cloudkitty CloudKitty] - OpenStack Rating as a Service component and usage reporting.
* [https://github.com/spilgames/ceilometer_graphite_publisher Graphite Publisher] - Ceilometer publisher to connect to Graphite.
* [https://github.com/openstack/watcher Watcher] - Resource optimization service.
* [http://icclab.github.io/cyclops Cyclops] - Rating-Charging-Billing Solution for Cloud providers.
* [https://github.com/gnocchixyz/collectd-gnocchi Collectd] - A Collectd writer plugin to publish telemetry to Gnocchi.

== Road Map ==
The future direction and plans of the project can be found [[Telemetry/RoadMap|here]]. Feel free to pick up a task if something interests you. Anyone is free to propose their own ideas in a patch as well.

== Contributing to Telemetry ==
The developer documentation can be found in each projects respective documentation page.

The telemetry project team hangs out on Freenode in the #openstack-telemetry channel, feel free to drop by and stay as long as you want. We use the [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Developers List] for our email discussions. If you want to make a post relevant to multiple projects in telemetry space,
please tag the subject with [telemetry]. If you have a post regarding a single project, please tag the subject with the appropriate tag: [aodh], [ceilometer], [gnocchi], or [panko].

The project team officially reserves a meeting slot but does not utilise it unless discussion items are raised to mailing list. see [[Meetings/Telemetry]].

[[Category:Telemetry]]

Telemetry

2017-12-06T18:23:26Z

Gordon chung: /* Panko */

= OpenStack Telemetry =

== Project Mission ==
To reliably collect data on the utilization of the physical and virtual resources comprising deployed clouds, persist these data for subsequent retrieval and analysis, and trigger actions when defined criteria are met.

== Services ==
The telemetry requirements of an OpenStack environment are vast and varied, they include use cases such as metering, monitoring, and alarming to name a few. The scope of these uses cases are diverse and beyond the scope of a single project and team. Currently, the telemetry project provides a set of functionality split across multiple projects; each project designed to provide a discrete service in the telemetry space.

=== Managed ===
The current set of projects are managed by the telemetry team are:
* [https://github.com/openstack/aodh Aodh] - an alarming service
* [https://github.com/openstack/ceilometer Ceilometer] - a data collection service
* [https://github.com/gnocchixyz/gnocchi Gnocchi] - a time-series database and resource indexing service
* [https://github.com/openstack/panko Panko] - an event, metadata indexing service

{| border="1" cellpadding="2" cellspacing="0"
| Specs
| https://github.com/openstack/ceilometer-specs
|-
| Admin doc
| http://docs.openstack.org/admin-guide-cloud/telemetry.html
|-
| Meetings
| https://wiki.openstack.org/wiki/Meetings/Telemetry
|}

Currently, a common spec repo and meeting time are shared between all managed projects

==== Aodh ====
* team lead - tbd
Aodh's goal is to enable the ability to trigger actions based on defined rules against sample or event data collected by Ceilometer

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/aodh
|-
| Bug tracker
| https://bugs.launchpad.net/aodh
|-
| Docs
| https://docs.openstack.org/aodh/latest/
|-
| Tarballs
| http://tarballs.openstack.org/aodh/
|}

==== Ceilometer ====
* team lead - Gordon Chung (gordc)
Ceilometer's goal is to efficiently collect, normalise and transform data produced by OpenStack services. The data it collects is intended to be used to create different views and help solve various telemetry use cases. Aodh and Gnocchi are two examples of services extending Ceilometer data.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/ceilometer
|-
| Bug tracker
| https://bugs.launchpad.net/ceilometer
|-
| Developer doc
| https://docs.openstack.org/ceilometer/latest/
|-
| Tarballs
| http://tarballs.openstack.org/ceilometer/
|}

==== Panko ====
* team lead - tbd
Panko is designed to provide a metadata indexing, event storage service which enables users to capture the state information of OpenStack resources at a given time. Its aim is to enable a scalable means of storing both short and long term data for use cases such as auditing and system debugging.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/panko
|-
| Bug tracker
| https://bugs.launchpad.net/panko
|-
| Docs
| https://docs.openstack.org/panko/latest/
|-
| Tarballs
| http://tarballs.openstack.org/panko/
|}

=== Externally Managed (Non-OpenStack) ===
==== Gnocchi ====

Gnocchi's goal is to provide a time-series resource indexing, metric storage service which enables users to capture OpenStack resources and the metrics associated with them. Using rolling aggregation set by user-defined archival policies, it's aim is to provide a scalable means of storing both short and long term data and provide a statistical view based on the input data (ie. Ceilometer)

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/gnocchixyz/gnocchi
|-
| Bug tracker
| https://github.com/gnocchixyz/gnocchi/issues
|-
| Developer doc
| http://gnocchi.xyz
|-
| Tarballs
| https://pypi.python.org/pypi/gnocchi
|}

=== Externally Managed ===
* [https://github.com/openstack/heat Heat] - Orchestration service which provides autoscaling capabilities using Ceilometer data.
* [https://github.com/openstack/horizon Horizon] - UI service which allows interaction with Aodh data.
* [https://github.com/stackforge/ceilometer-powervm PowerVM] - PowerVM pollster plugin. Owners: thorst and efried. IRC: #openstack-powervm
* [https://github.com/stackforge/cloudkitty CloudKitty] - OpenStack Rating as a Service component and usage reporting.
* [https://github.com/spilgames/ceilometer_graphite_publisher Graphite Publisher] - Ceilometer publisher to connect to Graphite.
* [https://github.com/openstack/watcher Watcher] - Resource optimization service.
* [http://icclab.github.io/cyclops Cyclops] - Rating-Charging-Billing Solution for Cloud providers.
* [https://github.com/gnocchixyz/collectd-gnocchi Collectd] - A Collectd writer plugin to publish telemetry to Gnocchi.

== Road Map ==
The future direction and plans of the project can be found [[Telemetry/RoadMap|here]]. Feel free to pick up a task if something interests you. Anyone is free to propose their own ideas in a patch as well.

== Contributing to Telemetry ==
The developer documentation can be found in each projects respective documentation page.

The telemetry project team hangs out on Freenode in the #openstack-telemetry channel, feel free to drop by and stay as long as you want. We use the [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Developers List] for our email discussions. If you want to make a post relevant to multiple projects in telemetry space,
please tag the subject with [telemetry]. If you have a post regarding a single project, please tag the subject with the appropriate tag: [aodh], [ceilometer], [gnocchi], or [panko].

The project team officially reserves a meeting slot but does not utilise it unless discussion items are raised to mailing list. see [[Meetings/Telemetry]].

[[Category:Telemetry]]

Telemetry

2017-12-06T18:23:03Z

Gordon chung: /* Ceilometer */

= OpenStack Telemetry =

== Project Mission ==
To reliably collect data on the utilization of the physical and virtual resources comprising deployed clouds, persist these data for subsequent retrieval and analysis, and trigger actions when defined criteria are met.

== Services ==
The telemetry requirements of an OpenStack environment are vast and varied, they include use cases such as metering, monitoring, and alarming to name a few. The scope of these uses cases are diverse and beyond the scope of a single project and team. Currently, the telemetry project provides a set of functionality split across multiple projects; each project designed to provide a discrete service in the telemetry space.

=== Managed ===
The current set of projects are managed by the telemetry team are:
* [https://github.com/openstack/aodh Aodh] - an alarming service
* [https://github.com/openstack/ceilometer Ceilometer] - a data collection service
* [https://github.com/gnocchixyz/gnocchi Gnocchi] - a time-series database and resource indexing service
* [https://github.com/openstack/panko Panko] - an event, metadata indexing service

{| border="1" cellpadding="2" cellspacing="0"
| Specs
| https://github.com/openstack/ceilometer-specs
|-
| Admin doc
| http://docs.openstack.org/admin-guide-cloud/telemetry.html
|-
| Meetings
| https://wiki.openstack.org/wiki/Meetings/Telemetry
|}

Currently, a common spec repo and meeting time are shared between all managed projects

==== Aodh ====
* team lead - tbd
Aodh's goal is to enable the ability to trigger actions based on defined rules against sample or event data collected by Ceilometer

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/aodh
|-
| Bug tracker
| https://bugs.launchpad.net/aodh
|-
| Docs
| https://docs.openstack.org/aodh/latest/
|-
| Tarballs
| http://tarballs.openstack.org/aodh/
|}

==== Ceilometer ====
* team lead - Gordon Chung (gordc)
Ceilometer's goal is to efficiently collect, normalise and transform data produced by OpenStack services. The data it collects is intended to be used to create different views and help solve various telemetry use cases. Aodh and Gnocchi are two examples of services extending Ceilometer data.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/ceilometer
|-
| Bug tracker
| https://bugs.launchpad.net/ceilometer
|-
| Developer doc
| https://docs.openstack.org/ceilometer/latest/
|-
| Tarballs
| http://tarballs.openstack.org/ceilometer/
|}

==== Panko ====
* team lead - tbd
Panko is designed to provide a metadata indexing, event storage service which enables users to capture the state information of OpenStack resources at a given time. Its aim is to enable a scalable means of storing both short and long term data for use cases such as auditing and system debugging.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/panko
|-
| Bug tracker
| https://bugs.launchpad.net/panko
|-
| Developer doc
| http://docs.openstack.org/developer/panko/
|-
| Tarballs
| http://tarballs.openstack.org/panko/
|}

=== Externally Managed (Non-OpenStack) ===
==== Gnocchi ====

Gnocchi's goal is to provide a time-series resource indexing, metric storage service which enables users to capture OpenStack resources and the metrics associated with them. Using rolling aggregation set by user-defined archival policies, it's aim is to provide a scalable means of storing both short and long term data and provide a statistical view based on the input data (ie. Ceilometer)

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/gnocchixyz/gnocchi
|-
| Bug tracker
| https://github.com/gnocchixyz/gnocchi/issues
|-
| Developer doc
| http://gnocchi.xyz
|-
| Tarballs
| https://pypi.python.org/pypi/gnocchi
|}

=== Externally Managed ===
* [https://github.com/openstack/heat Heat] - Orchestration service which provides autoscaling capabilities using Ceilometer data.
* [https://github.com/openstack/horizon Horizon] - UI service which allows interaction with Aodh data.
* [https://github.com/stackforge/ceilometer-powervm PowerVM] - PowerVM pollster plugin. Owners: thorst and efried. IRC: #openstack-powervm
* [https://github.com/stackforge/cloudkitty CloudKitty] - OpenStack Rating as a Service component and usage reporting.
* [https://github.com/spilgames/ceilometer_graphite_publisher Graphite Publisher] - Ceilometer publisher to connect to Graphite.
* [https://github.com/openstack/watcher Watcher] - Resource optimization service.
* [http://icclab.github.io/cyclops Cyclops] - Rating-Charging-Billing Solution for Cloud providers.
* [https://github.com/gnocchixyz/collectd-gnocchi Collectd] - A Collectd writer plugin to publish telemetry to Gnocchi.

== Road Map ==
The future direction and plans of the project can be found [[Telemetry/RoadMap|here]]. Feel free to pick up a task if something interests you. Anyone is free to propose their own ideas in a patch as well.

== Contributing to Telemetry ==
The developer documentation can be found in each projects respective documentation page.

The telemetry project team hangs out on Freenode in the #openstack-telemetry channel, feel free to drop by and stay as long as you want. We use the [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Developers List] for our email discussions. If you want to make a post relevant to multiple projects in telemetry space,
please tag the subject with [telemetry]. If you have a post regarding a single project, please tag the subject with the appropriate tag: [aodh], [ceilometer], [gnocchi], or [panko].

The project team officially reserves a meeting slot but does not utilise it unless discussion items are raised to mailing list. see [[Meetings/Telemetry]].

[[Category:Telemetry]]

Telemetry

2017-12-06T18:22:28Z

Gordon chung: /* Aodh */

= OpenStack Telemetry =

== Project Mission ==
To reliably collect data on the utilization of the physical and virtual resources comprising deployed clouds, persist these data for subsequent retrieval and analysis, and trigger actions when defined criteria are met.

== Services ==
The telemetry requirements of an OpenStack environment are vast and varied, they include use cases such as metering, monitoring, and alarming to name a few. The scope of these uses cases are diverse and beyond the scope of a single project and team. Currently, the telemetry project provides a set of functionality split across multiple projects; each project designed to provide a discrete service in the telemetry space.

=== Managed ===
The current set of projects are managed by the telemetry team are:
* [https://github.com/openstack/aodh Aodh] - an alarming service
* [https://github.com/openstack/ceilometer Ceilometer] - a data collection service
* [https://github.com/gnocchixyz/gnocchi Gnocchi] - a time-series database and resource indexing service
* [https://github.com/openstack/panko Panko] - an event, metadata indexing service

{| border="1" cellpadding="2" cellspacing="0"
| Specs
| https://github.com/openstack/ceilometer-specs
|-
| Admin doc
| http://docs.openstack.org/admin-guide-cloud/telemetry.html
|-
| Meetings
| https://wiki.openstack.org/wiki/Meetings/Telemetry
|}

Currently, a common spec repo and meeting time are shared between all managed projects

==== Aodh ====
* team lead - tbd
Aodh's goal is to enable the ability to trigger actions based on defined rules against sample or event data collected by Ceilometer

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/aodh
|-
| Bug tracker
| https://bugs.launchpad.net/aodh
|-
| Docs
| https://docs.openstack.org/aodh/latest/
|-
| Tarballs
| http://tarballs.openstack.org/aodh/
|}

==== Ceilometer ====
* team lead - Gordon Chung (gordc)
Ceilometer's goal is to efficiently collect, normalise and transform data produced by OpenStack services. The data it collects is intended to be used to create different views and help solve various telemetry use cases. Aodh and Gnocchi are two examples of services extending Ceilometer data.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/ceilometer
|-
| Blueprints
| https://blueprints.launchpad.net/ceilometer
|-
| Bug tracker
| https://bugs.launchpad.net/ceilometer
|-
| Developer doc
| http://docs.openstack.org/developer/ceilometer/
|-
| Tarballs
| http://tarballs.openstack.org/ceilometer/
|}

==== Panko ====
* team lead - tbd
Panko is designed to provide a metadata indexing, event storage service which enables users to capture the state information of OpenStack resources at a given time. Its aim is to enable a scalable means of storing both short and long term data for use cases such as auditing and system debugging.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/panko
|-
| Bug tracker
| https://bugs.launchpad.net/panko
|-
| Developer doc
| http://docs.openstack.org/developer/panko/
|-
| Tarballs
| http://tarballs.openstack.org/panko/
|}

=== Externally Managed (Non-OpenStack) ===
==== Gnocchi ====

Gnocchi's goal is to provide a time-series resource indexing, metric storage service which enables users to capture OpenStack resources and the metrics associated with them. Using rolling aggregation set by user-defined archival policies, it's aim is to provide a scalable means of storing both short and long term data and provide a statistical view based on the input data (ie. Ceilometer)

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/gnocchixyz/gnocchi
|-
| Bug tracker
| https://github.com/gnocchixyz/gnocchi/issues
|-
| Developer doc
| http://gnocchi.xyz
|-
| Tarballs
| https://pypi.python.org/pypi/gnocchi
|}

=== Externally Managed ===
* [https://github.com/openstack/heat Heat] - Orchestration service which provides autoscaling capabilities using Ceilometer data.
* [https://github.com/openstack/horizon Horizon] - UI service which allows interaction with Aodh data.
* [https://github.com/stackforge/ceilometer-powervm PowerVM] - PowerVM pollster plugin. Owners: thorst and efried. IRC: #openstack-powervm
* [https://github.com/stackforge/cloudkitty CloudKitty] - OpenStack Rating as a Service component and usage reporting.
* [https://github.com/spilgames/ceilometer_graphite_publisher Graphite Publisher] - Ceilometer publisher to connect to Graphite.
* [https://github.com/openstack/watcher Watcher] - Resource optimization service.
* [http://icclab.github.io/cyclops Cyclops] - Rating-Charging-Billing Solution for Cloud providers.
* [https://github.com/gnocchixyz/collectd-gnocchi Collectd] - A Collectd writer plugin to publish telemetry to Gnocchi.

== Road Map ==
The future direction and plans of the project can be found [[Telemetry/RoadMap|here]]. Feel free to pick up a task if something interests you. Anyone is free to propose their own ideas in a patch as well.

== Contributing to Telemetry ==
The developer documentation can be found in each projects respective documentation page.

The telemetry project team hangs out on Freenode in the #openstack-telemetry channel, feel free to drop by and stay as long as you want. We use the [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Developers List] for our email discussions. If you want to make a post relevant to multiple projects in telemetry space,
please tag the subject with [telemetry]. If you have a post regarding a single project, please tag the subject with the appropriate tag: [aodh], [ceilometer], [gnocchi], or [panko].

The project team officially reserves a meeting slot but does not utilise it unless discussion items are raised to mailing list. see [[Meetings/Telemetry]].

[[Category:Telemetry]]

Telemetry

2017-05-29T16:43:49Z

Gordon chung: /* Managed */

= OpenStack Telemetry =

== Project Mission ==
To reliably collect data on the utilization of the physical and virtual resources comprising deployed clouds, persist these data for subsequent retrieval and analysis, and trigger actions when defined criteria are met.

== Services ==
The telemetry requirements of an OpenStack environment are vast and varied, they include use cases such as metering, monitoring, and alarming to name a few. The scope of these uses cases are diverse and beyond the scope of a single project and team. Currently, the telemetry project provides a set of functionality split across multiple projects; each project designed to provide a discrete service in the telemetry space.

=== Managed ===
The current set of projects are managed by the telemetry team are:
* [https://github.com/openstack/aodh Aodh] - an alarming service
* [https://github.com/openstack/ceilometer Ceilometer] - a data collection service
* [https://github.com/gnocchixyz/gnocchi Gnocchi] - a time-series database and resource indexing service
* [https://github.com/openstack/panko Panko] - an event, metadata indexing service

{| border="1" cellpadding="2" cellspacing="0"
| Specs
| https://github.com/openstack/ceilometer-specs
|-
| Admin doc
| http://docs.openstack.org/admin-guide-cloud/telemetry.html
|-
| Meetings
| https://wiki.openstack.org/wiki/Meetings/Telemetry
|}

Currently, a common spec repo and meeting time are shared between all managed projects

==== Aodh ====
* team lead - Liusheng (liusheng)
Aodh's goal is to enable the ability to trigger actions based on defined rules against sample or event data collected by Ceilometer

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/aodh
|-
| Blueprints
| https://blueprints.launchpad.net/aodh
|-
| Bug tracker
| https://bugs.launchpad.net/aodh
|-
| Developer doc
| http://docs.openstack.org/developer/aodh/
|-
| Tarballs
| http://tarballs.openstack.org/aodh/
|}

==== Ceilometer ====
* team lead - Gordon Chung (gordc)
Ceilometer's goal is to efficiently collect, normalise and transform data produced by OpenStack services. The data it collects is intended to be used to create different views and help solve various telemetry use cases. Aodh and Gnocchi are two examples of services extending Ceilometer data.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/ceilometer
|-
| Blueprints
| https://blueprints.launchpad.net/ceilometer
|-
| Bug tracker
| https://bugs.launchpad.net/ceilometer
|-
| Developer doc
| http://docs.openstack.org/developer/ceilometer/
|-
| Tarballs
| http://tarballs.openstack.org/ceilometer/
|}

==== Panko ====
* team lead - tbd
Panko is designed to provide a metadata indexing, event storage service which enables users to capture the state information of OpenStack resources at a given time. Its aim is to enable a scalable means of storing both short and long term data for use cases such as auditing and system debugging.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/panko
|-
| Bug tracker
| https://bugs.launchpad.net/panko
|-
| Developer doc
| http://docs.openstack.org/developer/panko/
|-
| Tarballs
| http://tarballs.openstack.org/panko/
|}

=== Externally Managed (Non-OpenStack) ===
==== Gnocchi ====

Gnocchi's goal is to provide a time-series resource indexing, metric storage service which enables users to capture OpenStack resources and the metrics associated with them. Using rolling aggregation set by user-defined archival policies, it's aim is to provide a scalable means of storing both short and long term data and provide a statistical view based on the input data (ie. Ceilometer)

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/gnocchixyz/gnocchi
|-
| Bug tracker
| https://github.com/gnocchixyz/gnocchi/issues
|-
| Developer doc
| http://gnocchi.xyz
|-
| Tarballs
| https://pypi.python.org/pypi/gnocchi
|}

=== Externally Managed ===
* [https://github.com/openstack/heat Heat] - Orchestration service which provides autoscaling capabilities using Ceilometer data.
* [https://github.com/openstack/horizon Horizon] - UI service which allows interaction with Aodh data.
* [https://github.com/stackforge/ceilometer-powervm PowerVM] - PowerVM pollster plugin. Owners: thorst and efried. IRC: #openstack-powervm
* [https://github.com/stackforge/cloudkitty CloudKitty] - OpenStack Rating as a Service component and usage reporting.
* [https://github.com/spilgames/ceilometer_graphite_publisher Graphite Publisher] - Ceilometer publisher to connect to Graphite.
* [https://github.com/openstack/watcher Watcher] - Resource optimization service.
* [http://icclab.github.io/cyclops Cyclops] - Rating-Charging-Billing Solution for Cloud providers.
* [https://github.com/gnocchixyz/collectd-gnocchi Collectd] - A Collectd writer plugin to publish telemetry to Gnocchi.

== Road Map ==
The future direction and plans of the project can be found [[Telemetry/RoadMap|here]]. Feel free to pick up a task if something interests you. Anyone is free to propose their own ideas in a patch as well.

== Contributing to Telemetry ==
The developer documentation can be found in each projects respective documentation page.

The telemetry project team hangs out on Freenode in the #openstack-telemetry channel, feel free to drop by and stay as long as you want. We use the [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Developers List] for our email discussions. If you want to make a post relevant to multiple projects in telemetry space,
please tag the subject with [telemetry]. If you have a post regarding a single project, please tag the subject with the appropriate tag: [aodh], [ceilometer], [gnocchi], or [panko].

The project team officially reserves a meeting slot but does not utilise it unless discussion items are raised to mailing list. see [[Meetings/Telemetry]].

[[Category:Telemetry]]

Telemetry

2017-05-29T16:43:19Z

Gordon chung: /* OpenStack Telemetry */

= OpenStack Telemetry =

== Project Mission ==
To reliably collect data on the utilization of the physical and virtual resources comprising deployed clouds, persist these data for subsequent retrieval and analysis, and trigger actions when defined criteria are met.

== Services ==
The telemetry requirements of an OpenStack environment are vast and varied, they include use cases such as metering, monitoring, and alarming to name a few. The scope of these uses cases are diverse and beyond the scope of a single project and team. Currently, the telemetry project provides a set of functionality split across multiple projects; each project designed to provide a discrete service in the telemetry space.

=== Managed ===
The current set of projects are managed by the telemetry team are:
* [https://github.com/openstack/aodh Aodh] - an alarming service
* [https://github.com/openstack/ceilometer Ceilometer] - a data collection service
* [https://github.com/openstack/gnocchi Gnocchi] - a time-series database and resource indexing service
* [https://github.com/openstack/panko Panko] - an event, metadata indexing service

{| border="1" cellpadding="2" cellspacing="0"
| Specs
| https://github.com/openstack/ceilometer-specs
|-
| Admin doc
| http://docs.openstack.org/admin-guide-cloud/telemetry.html
|-
| Meetings
| https://wiki.openstack.org/wiki/Meetings/Telemetry
|}

Currently, a common spec repo and meeting time are shared between all managed projects

==== Aodh ====
* team lead - Liusheng (liusheng)
Aodh's goal is to enable the ability to trigger actions based on defined rules against sample or event data collected by Ceilometer

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/aodh
|-
| Blueprints
| https://blueprints.launchpad.net/aodh
|-
| Bug tracker
| https://bugs.launchpad.net/aodh
|-
| Developer doc
| http://docs.openstack.org/developer/aodh/
|-
| Tarballs
| http://tarballs.openstack.org/aodh/
|}

==== Ceilometer ====
* team lead - Gordon Chung (gordc)
Ceilometer's goal is to efficiently collect, normalise and transform data produced by OpenStack services. The data it collects is intended to be used to create different views and help solve various telemetry use cases. Aodh and Gnocchi are two examples of services extending Ceilometer data.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/ceilometer
|-
| Blueprints
| https://blueprints.launchpad.net/ceilometer
|-
| Bug tracker
| https://bugs.launchpad.net/ceilometer
|-
| Developer doc
| http://docs.openstack.org/developer/ceilometer/
|-
| Tarballs
| http://tarballs.openstack.org/ceilometer/
|}

==== Panko ====
* team lead - tbd
Panko is designed to provide a metadata indexing, event storage service which enables users to capture the state information of OpenStack resources at a given time. Its aim is to enable a scalable means of storing both short and long term data for use cases such as auditing and system debugging.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/panko
|-
| Bug tracker
| https://bugs.launchpad.net/panko
|-
| Developer doc
| http://docs.openstack.org/developer/panko/
|-
| Tarballs
| http://tarballs.openstack.org/panko/
|}

=== Externally Managed (Non-OpenStack) ===
==== Gnocchi ====

Gnocchi's goal is to provide a time-series resource indexing, metric storage service which enables users to capture OpenStack resources and the metrics associated with them. Using rolling aggregation set by user-defined archival policies, it's aim is to provide a scalable means of storing both short and long term data and provide a statistical view based on the input data (ie. Ceilometer)

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/gnocchixyz/gnocchi
|-
| Bug tracker
| https://github.com/gnocchixyz/gnocchi/issues
|-
| Developer doc
| http://gnocchi.xyz
|-
| Tarballs
| https://pypi.python.org/pypi/gnocchi
|}

=== Externally Managed ===
* [https://github.com/openstack/heat Heat] - Orchestration service which provides autoscaling capabilities using Ceilometer data.
* [https://github.com/openstack/horizon Horizon] - UI service which allows interaction with Aodh data.
* [https://github.com/stackforge/ceilometer-powervm PowerVM] - PowerVM pollster plugin. Owners: thorst and efried. IRC: #openstack-powervm
* [https://github.com/stackforge/cloudkitty CloudKitty] - OpenStack Rating as a Service component and usage reporting.
* [https://github.com/spilgames/ceilometer_graphite_publisher Graphite Publisher] - Ceilometer publisher to connect to Graphite.
* [https://github.com/openstack/watcher Watcher] - Resource optimization service.
* [http://icclab.github.io/cyclops Cyclops] - Rating-Charging-Billing Solution for Cloud providers.
* [https://github.com/gnocchixyz/collectd-gnocchi Collectd] - A Collectd writer plugin to publish telemetry to Gnocchi.

== Road Map ==
The future direction and plans of the project can be found [[Telemetry/RoadMap|here]]. Feel free to pick up a task if something interests you. Anyone is free to propose their own ideas in a patch as well.

== Contributing to Telemetry ==
The developer documentation can be found in each projects respective documentation page.

The telemetry project team hangs out on Freenode in the #openstack-telemetry channel, feel free to drop by and stay as long as you want. We use the [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Developers List] for our email discussions. If you want to make a post relevant to multiple projects in telemetry space,
please tag the subject with [telemetry]. If you have a post regarding a single project, please tag the subject with the appropriate tag: [aodh], [ceilometer], [gnocchi], or [panko].

The project team officially reserves a meeting slot but does not utilise it unless discussion items are raised to mailing list. see [[Meetings/Telemetry]].

[[Category:Telemetry]]

Telemetry/RoadMap

2017-05-29T16:37:45Z

Gordon chung: /* Open Work Items */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active

=== All Projects ===
* service status interface
** raise details on health, message processing rate, etc...

=== Aodh (alarming) ===
* [https://bugs.launchpad.net/aodh/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* alarm CRUD events
* send aodh CRUD events to panko
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* [https://bugs.launchpad.net/ceilometer/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* deprecate ceilometer-api
** document how to push to gnocchi or use HTTP dispatcher
* generic notification agent
* rolling upgrades test gate
* rally tests

=== Panko (event storage) ===
* [https://bugs.launchpad.net/panko/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* tempest tests

=== Gnocchi (metric storage) ===
* NOTE: Gnocchi has moved outside of OpenStack scope. It is developed outside of OpenStack but will remain compatible.
* Issues tracked at [https://github.com/gnocchixyz/gnocchi/issues gnocchi github]

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2017-05-29T16:36:42Z

Gordon chung: /* Open Work Items */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active

=== All Projects ===
* service status interface
** raise details on health, message processing rate, etc...

=== Aodh (alarming) ===
* [https://bugs.launchpad.net/aodh/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* alarm CRUD events
* send aodh CRUD events to panko
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* [https://bugs.launchpad.net/ceilometer/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* deprecate ceilometer-api
** document how to push to gnocchi or use HTTP dispatcher
* generic notification agent
* rolling upgrades test gate
* rally tests

=== Panko (event storage) ===
* [https://bugs.launchpad.net/panko/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* tempest tests

NOTE: Gnocchi has moved outside of OpenStack scope. It is developed outside of OpenStack but will remain compatible.

=== Gnocchi (metric storage) ===
* Issues tracked at [https://github.com/gnocchixyz/gnocchi/issues gnocchi github]

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2017-03-23T15:38:39Z

Gordon chung: /* Gnocchi (metric storage) */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== All Projects ===
* service status interface
** raise details on health, message processing rate, etc...

=== Aodh (alarming) ===
* [https://bugs.launchpad.net/aodh/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* alarm CRUD events
* send aodh CRUD events to panko
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* [https://bugs.launchpad.net/ceilometer/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* deprecate ceilometer-api
** document how to push to gnocchi or use HTTP dispatcher
* generic notification agent
* rolling upgrades test gate
* rally tests

=== Gnocchi (metric storage) ===
* [https://bugs.launchpad.net/gnocchi/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* indexer sharding support (maybe?)
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* migrate tempest plugin

=== Panko (event storage) ===
* [https://bugs.launchpad.net/panko/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* tempest tests

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2017-02-28T14:12:30Z

Gordon chung: /* Road Map */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== All Projects ===
* service status interface
** raise details on health, message processing rate, etc...

=== Aodh (alarming) ===
* [https://bugs.launchpad.net/aodh/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* alarm CRUD events
* send aodh CRUD events to panko
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* [https://bugs.launchpad.net/ceilometer/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* deprecate ceilometer-api
** document how to push to gnocchi or use HTTP dispatcher
* generic notification agent
* rolling upgrades test gate
* rally tests

=== Gnocchi (metric storage) ===
* [https://bugs.launchpad.net/gnocchi/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* indexer sharding support (maybe?)
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* fair scheduling
* migrate tempest plugin

=== Panko (event storage) ===
* [https://bugs.launchpad.net/panko/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* tempest tests

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2017-02-07T16:03:47Z

Gordon chung: /* Gnocchi (metric storage) */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

Current (Ocata) Cycle Targets: https://blueprints.launchpad.net/ceilometer/ocata

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== All Projects ===
* service status interface
** raise details on health, message processing rate, etc...

=== Aodh (alarming) ===
* [https://bugs.launchpad.net/aodh/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* alarm CRUD events
* send aodh CRUD events to panko
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* [https://bugs.launchpad.net/ceilometer/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* multiple meter/event definition file support
* deprecate ceilometer-api
** document how to push to gnocchi or use HTTP dispatcher
* remove ceilometer collector
** clean from gnocchi_resources.yaml as well
* generic notification agent
* rolling upgrades test gate
* rally tests

=== Gnocchi (metric storage) ===
* [https://bugs.launchpad.net/gnocchi/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* indexer sharding support (maybe?)
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* fair scheduling
* migrate tempest plugin

=== Panko (event storage) ===
* [https://bugs.launchpad.net/panko/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* tempest tests

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2017-01-26T22:18:32Z

Gordon chung: /* Ceilometer (data collection) */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

Current (Ocata) Cycle Targets: https://blueprints.launchpad.net/ceilometer/ocata

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== All Projects ===
* service status interface
** raise details on health, message processing rate, etc...

=== Aodh (alarming) ===
* [https://bugs.launchpad.net/aodh/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* alarm CRUD events
* send aodh CRUD events to panko
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* [https://bugs.launchpad.net/ceilometer/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* multiple meter/event definition file support
* deprecate ceilometer-api
** document how to push to gnocchi or use HTTP dispatcher
* remove ceilometer collector
** clean from gnocchi_resources.yaml as well
* generic notification agent
* rolling upgrades test gate
* rally tests

=== Gnocchi (metric storage) ===
* [https://bugs.launchpad.net/gnocchi/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* indexer sharding support
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* project unique resource_id
* fair scheduling
* migrate tempest plugin

=== Panko (event storage) ===
* [https://bugs.launchpad.net/panko/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* tempest tests

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2017-01-26T22:11:35Z

Gordon chung: /* Panko (event storage) */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

Current (Ocata) Cycle Targets: https://blueprints.launchpad.net/ceilometer/ocata

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== All Projects ===
* service status interface
** raise details on health, message processing rate, etc...

=== Aodh (alarming) ===
* [https://bugs.launchpad.net/aodh/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* alarm CRUD events
* send aodh CRUD events to panko
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* [https://bugs.launchpad.net/ceilometer/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* multiple meter/event definition file support
* refine polling
** drop metadata polling requirements
* deprecate ceilometer-api
** document how to push to gnocchi or use HTTP dispatcher
* remove ceilometer collector
** clean from gnocchi_resources.yaml as well
* generic notification agent
* rolling upgrades test gate
* rally tests

=== Gnocchi (metric storage) ===
* [https://bugs.launchpad.net/gnocchi/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* indexer sharding support
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* project unique resource_id
* fair scheduling
* migrate tempest plugin

=== Panko (event storage) ===
* [https://bugs.launchpad.net/panko/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* tempest tests

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2017-01-26T22:11:15Z

Gordon chung: /* Aodh (alarming) */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

Current (Ocata) Cycle Targets: https://blueprints.launchpad.net/ceilometer/ocata

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== All Projects ===
* service status interface
** raise details on health, message processing rate, etc...

=== Aodh (alarming) ===
* [https://bugs.launchpad.net/aodh/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* alarm CRUD events
* send aodh CRUD events to panko
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* [https://bugs.launchpad.net/ceilometer/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* multiple meter/event definition file support
* refine polling
** drop metadata polling requirements
* deprecate ceilometer-api
** document how to push to gnocchi or use HTTP dispatcher
* remove ceilometer collector
** clean from gnocchi_resources.yaml as well
* generic notification agent
* rolling upgrades test gate
* rally tests

=== Gnocchi (metric storage) ===
* [https://bugs.launchpad.net/gnocchi/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* indexer sharding support
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* project unique resource_id
* fair scheduling
* migrate tempest plugin

=== Panko (event storage) ===
* [https://bugs.launchpad.net/panko/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* ?

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2017-01-05T16:06:45Z

Gordon chung: /* Gnocchi (metric storage) */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

Current (Ocata) Cycle Targets: https://blueprints.launchpad.net/ceilometer/ocata

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== All Projects ===
* service status interface
** raise details on health, message processing rate, etc...

=== Aodh (alarming) ===
* [https://bugs.launchpad.net/aodh/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* alarm CRUD events
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* [https://bugs.launchpad.net/ceilometer/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* multiple meter/event definition file support
* refine polling
** drop metadata polling requirements
* deprecate ceilometer-api
** document how to push to gnocchi or use HTTP dispatcher
* remove ceilometer collector
** clean from gnocchi_resources.yaml as well
* generic notification agent
* rolling upgrades test gate
* rally tests

=== Gnocchi (metric storage) ===
* [https://bugs.launchpad.net/gnocchi/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* indexer sharding support
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* project unique resource_id
* fair scheduling
* migrate tempest plugin

=== Panko (event storage) ===
* [https://bugs.launchpad.net/panko/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* ?

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2016-12-07T15:52:36Z

Gordon chung: /* Ceilometer (data collection) */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

Current (Ocata) Cycle Targets: https://blueprints.launchpad.net/ceilometer/ocata

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== All Projects ===
* service status interface
** raise details on health, message processing rate, etc...

=== Aodh (alarming) ===
* [https://bugs.launchpad.net/aodh/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* alarm CRUD events
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* [https://bugs.launchpad.net/ceilometer/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* multiple meter/event definition file support
* refine polling
** drop metadata polling requirements
* deprecate ceilometer-api
** document how to push to gnocchi or use HTTP dispatcher
* remove ceilometer collector
** clean from gnocchi_resources.yaml as well
* generic notification agent
* rolling upgrades test gate
* rally tests

=== Gnocchi (metric storage) ===
* [https://bugs.launchpad.net/gnocchi/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* indexer sharding support
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* project unique resource_id
* fair scheduling
* dynamic granularity aggregates
* migrate tempest plugin

=== Panko (event storage) ===
* [https://bugs.launchpad.net/panko/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* ?

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry

2016-11-07T22:21:44Z

Gordon chung: /* Managed */

= OpenStack Telemetry =

== Project Mission ==
To reliably collect data on the utilization of the physical and virtual resources comprising deployed clouds, persist these data for subsequent retrieval and analysis, and trigger actions when defined criteria are met.

== Services ==
The telemetry requirements of an OpenStack environment are vast and varied, they include use cases such as metering, monitoring, and alarming to name a few. The scope of these uses cases are diverse and beyond the scope of a single project and team. Currently, the telemetry project provides a set of functionality split across multiple projects; each project designed to provide a discrete service in the telemetry space.

=== Managed ===
The current set of projects are managed by the telemetry team are:
* [https://github.com/openstack/aodh Aodh] - an alarming service
* [https://github.com/openstack/ceilometer Ceilometer] - a data collection service
* [https://github.com/openstack/gnocchi Gnocchi] - a time-series database and resource indexing service
* [https://github.com/openstack/panko Panko] - an event, metadata indexing service

{| border="1" cellpadding="2" cellspacing="0"
| Specs
| https://github.com/openstack/ceilometer-specs
|-
| Admin doc
| http://docs.openstack.org/admin-guide-cloud/telemetry.html
|-
| Meetings
| https://wiki.openstack.org/wiki/Meetings/Telemetry
|}

Currently, a common spec repo and meeting time are shared between all managed projects

==== Aodh ====
* team lead - Liusheng (liusheng)
Aodh's goal is to enable the ability to trigger actions based on defined rules against sample or event data collected by Ceilometer

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/aodh
|-
| Blueprints
| https://blueprints.launchpad.net/aodh
|-
| Bug tracker
| https://bugs.launchpad.net/aodh
|-
| Developer doc
| http://docs.openstack.org/developer/aodh/
|-
| Tarballs
| http://tarballs.openstack.org/aodh/
|}

==== Ceilometer ====
* team lead - Gordon Chung (gordc)
Ceilometer's goal is to efficiently collect, normalise and transform data produced by OpenStack services. The data it collects is intended to be used to create different views and help solve various telemetry use cases. Aodh and Gnocchi are two examples of services extending Ceilometer data.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/ceilometer
|-
| Blueprints
| https://blueprints.launchpad.net/ceilometer
|-
| Bug tracker
| https://bugs.launchpad.net/ceilometer
|-
| Developer doc
| http://docs.openstack.org/developer/ceilometer/
|-
| Tarballs
| http://tarballs.openstack.org/ceilometer/
|}

==== Gnocchi ====
* team lead - Julien Danjou (jd__)
Gnocchi's goal is to provide a time-series resource indexing, metric storage service which enables users to capture OpenStack resources and the metrics associated with them. Using rolling aggregation set by user-defined archival policies, it's aim is to provide a scalable means of storing both short and long term data and provide a statistical view based on the input data (ie. Ceilometer)

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/gnocchi
|-
| Bug tracker
| https://bugs.launchpad.net/gnocchi
|-
| Developer doc
| http://docs.openstack.org/developer/gnocchi/
|-
| Tarballs
| http://tarballs.openstack.org/gnocchi/
|}

==== Panko ====
* team lead - tbd
Panko is designed to provide a metadata indexing, event storage service which enables users to capture the state information of OpenStack resources at a given time. Its aim is to enable a scalable means of storing both short and long term data for use cases such as auditing and system debugging.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/panko
|-
| Bug tracker
| https://bugs.launchpad.net/panko
|-
| Developer doc
| http://docs.openstack.org/developer/panko/
|-
| Tarballs
| http://tarballs.openstack.org/panko/
|}

=== Externally Managed ===
* [https://github.com/openstack/heat Heat] - Orchestration service which provides autoscaling capabilities using Ceilometer data.
* [https://github.com/openstack/horizon Horizon] - UI service which allows interaction with Aodh data.
* [https://github.com/stackforge/ceilometer-powervm PowerVM] - PowerVM pollster plugin. Owners: thorst and efried. IRC: #openstack-powervm
* [https://github.com/stackforge/cloudkitty CloudKitty] - OpenStack Rating as a Service component and usage reporting.
* [https://github.com/spilgames/ceilometer_graphite_publisher Graphite Publisher] - Ceilometer publisher to connect to Graphite.
* [https://github.com/openstack/watcher Watcher] - Resource optimization service.
* [http://icclab.github.io/cyclops Cyclops] - Rating-Charging-Billing Solution for Cloud providers.
* [https://github.com/openstack/collectd-ceilometer-plugin Collectd] - A Collectd writer plugin to publish telemetry to Ceilometer.

== Road Map ==
The future direction and plans of the project can be found [[Telemetry/RoadMap|here]]. Feel free to pick up a task if something interests you. Anyone is free to propose their own ideas in a spec as well.

== Contributing to Telemetry ==
The developer documentation can be found in each projects respective documentation page.

The telemetry project team hangs out on Freenode in the #openstack-telemetry channel, feel free to drop by and stay as long as you want. We use the [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Developers List] for our email discussions. If you want to make a post relevant to multiple projects in telemetry space,
please tag the subject with [telemetry]. If you have a post regarding a single project, please tag the subject with the appropriate tag: [aodh], [ceilometer] or [gnocchi].

The project team officially meets once a week, see [[Meetings/Telemetry]].

[[Category:Telemetry]]

Telemetry/RoadMap

2016-11-02T13:38:05Z

Gordon chung: /* Open Work Items */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

Current (Ocata) Cycle Targets: https://blueprints.launchpad.net/ceilometer/ocata

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== All Projects ===
* service status interface
** raise details on health, message processing rate, etc...

=== Aodh (alarming) ===
* [https://bugs.launchpad.net/aodh/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* alarm CRUD events
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* [https://bugs.launchpad.net/ceilometer/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* multiple meter/event definition file support
* refine polling
** drop metadata polling requirements
* deprecate ceilometer-api
** document how to push to gnocchi or use HTTP dispatcher
* remove ceilometer collector
* cleanup publisher/dispatcher duplicity
* remove volume=1 pollsters
** clean from gnocchi_resources.yaml as well
* generic notification agent
* rolling upgrades test gate
* rally tests

=== Gnocchi (metric storage) ===
* [https://bugs.launchpad.net/gnocchi/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* indexer sharding support
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* project unique resource_id
* fair scheduling
* dynamic granularity aggregates
* migrate tempest plugin

=== Panko (event storage) ===
* [https://bugs.launchpad.net/panko/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* ?

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2016-11-02T13:36:35Z

Gordon chung: /* Open Work Items */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

Current (Ocata) Cycle Targets: https://blueprints.launchpad.net/ceilometer/ocata

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== All Projects ===
* service status interface
** raise details on health, message processing rate, etc...

=== Aodh (alarming) ===
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* alarm CRUD events
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* multiple meter/event definition file support
* refine polling
** drop metadata polling requirements
* deprecate ceilometer-api
** document how to push to gnocchi or use HTTP dispatcher
* remove ceilometer collector
* cleanup publisher/dispatcher duplicity
* remove volume=1 pollsters
** clean from gnocchi_resources.yaml as well
* generic notification agent
* rolling upgrades test gate
* rally tests

=== Gnocchi (metric storage) ===
* [https://bugs.launchpad.net/gnocchi/+bugs?field.importance%3Alist=WISHLIST wishlist items]
* indexer sharding support
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* project unique resource_id
* fair scheduling
* dynamic granularity aggregates
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2016-11-02T13:26:23Z

Gordon chung: /* Gnocchi (metric storage) */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

Current (Ocata) Cycle Targets: https://blueprints.launchpad.net/ceilometer/ocata

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* multiple meter/event definition file support
* refine polling
** drop metadata polling requirements
* deprecate ceilometer-api
* generic notification agent
* rally tests

=== Gnocchi (metric storage) ===
* [https://bugs.launchpad.net/gnocchi/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.importance%3Alist=WISHLIST&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on wishlist items]
* indexer sharding support
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* project unique resource_id
* fair scheduling
* dynamic granularity aggregates
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2016-11-02T13:26:06Z

Gordon chung: /* Gnocchi (metric storage) */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

Current (Ocata) Cycle Targets: https://blueprints.launchpad.net/ceilometer/ocata

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* multiple meter/event definition file support
* refine polling
** drop metadata polling requirements
* deprecate ceilometer-api
* generic notification agent
* rally tests

=== Gnocchi (metric storage) ===
* indexer sharding support
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* project unique resource_id
* fair scheduling
* dynamic granularity aggregates
* [https://bugs.launchpad.net/gnocchi/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.importance%3Alist=WISHLIST&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on wishlist items]
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2016-11-02T13:21:29Z

Gordon chung: /* Road Map */

= Road Map =

'''NOTE:''' We do not use blueprints in Telemetry projects. If a patch is complex or controversial, please raise the topic to the mailing list using the ''[telemetry]'' tag. In very rare cases will a spec or blueprint be required.

Current (Ocata) Cycle Targets: https://blueprints.launchpad.net/ceilometer/ocata

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* adopt oslo.db pagination

=== Ceilometer (data collection) ===
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* multiple meter/event definition file support
* refine polling
** drop metadata polling requirements
* deprecate ceilometer-api
* generic notification agent
* rally tests

=== Gnocchi (metric storage) ===
* indexer sharding support
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* project unique resource_id
* [https://bugs.launchpad.net/gnocchi/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.importance%3Alist=WISHLIST&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on wishlist items]
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in aodh
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Newton: https://blueprints.launchpad.net/ceilometer/newton
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Gnocchi

2016-08-24T19:26:46Z

Gordon chung: /* Gnocchi */

= Gnocchi =

Gnocchi is the project name of a TDBaaS (Time Series Database as a Service) project started under the Ceilometer program umbrella.

<b>NOTE: The information below is historical and reflect the state of the project during its origin. For up to date information, please visit the [http://gnocchi.xyz official documentation]</b>

== Motivation ==

From the beginning of the Ceilometer project, a large part of the goal was to store time series data that were collected. In the early stages of the project, it wasn't really clear what and how these time series were going to be handled, manipulated and queried, so the data model used by Ceilometer was very flexible. That ended up being really powerful and handy, but the resulting performance has been terrible, to a point where storing a large amount of metrics on several weeks is really hard to achieve without having the data storage backend collapsing.

Having such a flexible data model and query system is great, but in the end users are doing the same request over and over and the use cases that need to be addressed are a subset of that data model. On the other hand, some queries and use cases are not solved by the current data model, either because they are not easy to be expressed or because they are just too damn slow to run.

Lately, during the Icehouse Design Summit in Hong-Kong, developers and users showed interest in having Ceilometer doing metric data aggregation, in order to keep data in a more long running fashion. No work has been done during the Icehouse cycle on that, probably due to the lack of manpower around the idea, even if the idea and motivation was validated by the core team back then.

Considering the amount of data and metrics Ceilometer generates and has to store, a new strategy and a rethinking of the problem was needed, so Gnocchi is a try on that.

== Rethinking the problem ==

Ceilometer is nowadays trying to achieve two different things:

* Store metrics, that is a list of (timestamp, value) for a given entity, this entity being anything from the temperature in your datacenter to the CPU usage of a VM.
* Store events, that is a list of things that happens in your OpenStack installation: an API request has been received, a VM has been started, an image has been uploaded, a server fell of the roof, whatever

These two things are both very useful for all the use cases Ceilometer tries to achieve. Metrics are useful for monitoring, billing and alarming, where events are useful to do audit, performance analysis, debugging, etc.

However, while the event collection of Ceilometer is pretty solid and ok (but still needs to be working on), the metrics part suffers terrible design and performance issues.

Having the so called free form metadata associated with each metric generated by Ceilometer is the most problematic design we have. It stores a lot of redundant information that it is hard to query in a efficient manner. On the other hand, systems like RRD have existed for a while, storing a large amount of (aggregated) metrics without much problem. The metadata associated to these metrics being another issue.

So that left us with two different problem to solve: Store metrics and store information (the so called metadata) about resources.

== Prototype implementation (OUTDATED) ==

jd has started a prototype of that solution with the Gnocchi project. It provides a time series storage and a resource indexer, which are both fast and scalable.

It provides a REST API. The REST API provides two types of resources:

* Entity, which are things you can measure.
* A resource, which has various information, and is linked to any number of entities.

Here's how the software is architected.

[[File:Gnocchi architecture.png|center]]

The two types of objects managed and provided by Gnocchi are stored in two different data stores, because these two types of things are definitely different. Relying on the same type of data storage would break things, just like what we saw in Ceilometer.

=== Time series storage ===
Like in Ceilometer the storage driver is abstracted so you can write your own using whatever technology you want.

The storage driver is in charge of storing the metric in an aggregated manner. Yes that means you aggregate according to what the user requested when they created the entity, before you store the metrics.

The canonical implementation of the time series storage is based on the use of [http://pandas.pydata.org/ Pandas] and Swift. For the record, the first version was based on [http://graphite.wikidot.com/whisper Whisper], but it turned out to be a bad option (terrible base code which also has a lot of assumption about using file based storage). Using pandas and building our own serialization format is much better.

Swift provides an almost infinite of space to store data, is likely already part of your cloud (so it's not something else to deploy for your operators) and it is very scalable.

=== Resource indexer ===
Like for the TSD, the driver is abstracted.

The canonical implementation is based on SQLAlchemy, just because SQL is fast, indexable, etc. So it's a great storage for that. And SQL is already deployed in your OpenStack environment, so again: It's not yet another thing to deploy.

The plan is to describe some resources (instances, images, etc) so they have real schemas that can be indexed and queried efficiently.

=== Current REST API ===
The API is still evolving for now. We currently have this:

* '''POST /v1/entity''': create an entity. You have to specify the list of archives you want to store. An archive is composed of a tuple (granularity, number of measures). It defines the number of measure you want to keep and how often you want them. For example, (5, 60) will store 60 measure with a granularity of 5 seconds.
* '''DELETE /v1/entity''': delete an entity
* '''POST /v1/entity/<name>/measures''': post a list of {timestamp: <ts>, value: <v>} to store as measurements
* '''GET /v1/entity/<name>/measures''': get the list of measures for this entity. You can specify an interval with start= and stop=, and the type of aggregation you want to retrieve (mean, median, last, min, max, first…)

* '''POST /v1/resources''': create a resource

And I'm still working on that for now.

Meetings/Telemetry

2016-08-04T18:47:46Z

Gordon chung: /* Apologies for absence */

= Mid-Cycles =

The telemetry team will not hold a midcycle for Mitaka. A virtual one will be discussed for January if required.

Past Midcycles

* [[Meetings/Ceilometer/Liberty Virtual Mid-Cycle|Liberty Virtual Mid-Cycle]]

= Telemetry meetings =
The telemetry project team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code> when specific items to discuss are placed on agenda. The meetings run on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].

Everyone is welcome.

The blueprints that are used as a basis for the telemetry project can be found [https://blueprints.launchpad.net/ceilometer here]. We are currently sharing the ceilometer space until aodh and gnocchi requirements warrant segregated management. For now, to ensure collaboration, the space will remain shared.

The process of proposing a new blueprint from Juno onwards is described [https://wiki.openstack.org/wiki/Blueprints#Blueprints_and_Specs here].

=== Agenda ===

'''Please add your name with the agenda item, so we know who to call on during the meeting.'''

Specific item to discuss:
* None

Usual agenda:
* release candidate blockers
* recurring: roadmap items (new/old/blockers) https://wiki.openstack.org/wiki/Telemetry/RoadMap
* aodh topics
* ceilometer topics
* gnocchi topics
* Open discussion

=== Apologies for absence ===

== Previous meetings ==
* [http://eavesdrop.openstack.org/meetings/telemetry/2016 2016]
* [http://eavesdrop.openstack.org/meetings/telemetry/2015 2015]

=== HIstorical Ceilometer meetings ===
* [http://eavesdrop.openstack.org/meetings/ceilometer/2015 2015]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2014 2014]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2013 2013]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2012 2012]

=== Historical pre-Ceilometer meetings ===
* meeting 16 | 16 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.html summary]
* meeting 15 | 09 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.html summary]
* meeting 14 | 02 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.html summary]
* meeting 13 | 26 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.html summary]
* meeting 12 | 19 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.html summary]
* meeting 11 | 12 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.log.html log]
* meeting 10 | 05 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.log.html log]
* meeting 9 | 28 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.log.html log]
* meeting 8 | 21 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.log.html log]
* meeting 7 | 13 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.log.html log]
* meeting 6 | 7 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.log.html log]
* meeting 5 | 31 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.log.html log]
* meeting 4 | 24 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.log.html log]
* meeting 3 | 17 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.log.html log]
* meeting 2 | 10 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html log]
* meeting 1 | 3 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.log.html log]
* meeting 0 | 26 apr 12 | [[Meetings/MeteringAgenda/meeting-0-summary|summary]] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.log.html log]

== Meeting organizers ==
* Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
* Use http://meetbot.debian.net/Manual.html to get an automatic summary
* Prepare an outline for the meeting to speed things up
<pre><nowiki>
#startmeeting telemetry
#topic some action from previous meeting
#topic something interesting
#topic Open discussion
#endmeeting
</nowiki></pre>

* Update == Agenda for next meeting ==
* Mail the automatic summary as a reply to the invitation

Meetings/Telemetry

2016-08-04T16:59:55Z

Gordon chung: /* Weekly Telemetry meeting */

= Mid-Cycles =

The telemetry team will not hold a midcycle for Mitaka. A virtual one will be discussed for January if required.

Past Midcycles

* [[Meetings/Ceilometer/Liberty Virtual Mid-Cycle|Liberty Virtual Mid-Cycle]]

= Telemetry meetings =
The telemetry project team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code> when specific items to discuss are placed on agenda. The meetings run on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].

Everyone is welcome.

The blueprints that are used as a basis for the telemetry project can be found [https://blueprints.launchpad.net/ceilometer here]. We are currently sharing the ceilometer space until aodh and gnocchi requirements warrant segregated management. For now, to ensure collaboration, the space will remain shared.

The process of proposing a new blueprint from Juno onwards is described [https://wiki.openstack.org/wiki/Blueprints#Blueprints_and_Specs here].

=== Agenda ===

'''Please add your name with the agenda item, so we know who to call on during the meeting.'''

Specific item to discuss:
* None

Usual agenda:
* release candidate blockers
* recurring: roadmap items (new/old/blockers) https://wiki.openstack.org/wiki/Telemetry/RoadMap
* aodh topics
* ceilometer topics
* gnocchi topics
* Open discussion

=== Apologies for absence ===
llu: 3/26 - 4/4, take vacation

== Previous meetings ==
* [http://eavesdrop.openstack.org/meetings/telemetry/2016 2016]
* [http://eavesdrop.openstack.org/meetings/telemetry/2015 2015]

=== HIstorical Ceilometer meetings ===
* [http://eavesdrop.openstack.org/meetings/ceilometer/2015 2015]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2014 2014]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2013 2013]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2012 2012]

=== Historical pre-Ceilometer meetings ===
* meeting 16 | 16 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.html summary]
* meeting 15 | 09 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.html summary]
* meeting 14 | 02 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.html summary]
* meeting 13 | 26 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.html summary]
* meeting 12 | 19 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.html summary]
* meeting 11 | 12 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.log.html log]
* meeting 10 | 05 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.log.html log]
* meeting 9 | 28 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.log.html log]
* meeting 8 | 21 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.log.html log]
* meeting 7 | 13 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.log.html log]
* meeting 6 | 7 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.log.html log]
* meeting 5 | 31 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.log.html log]
* meeting 4 | 24 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.log.html log]
* meeting 3 | 17 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.log.html log]
* meeting 2 | 10 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html log]
* meeting 1 | 3 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.log.html log]
* meeting 0 | 26 apr 12 | [[Meetings/MeteringAgenda/meeting-0-summary|summary]] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.log.html log]

== Meeting organizers ==
* Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
* Use http://meetbot.debian.net/Manual.html to get an automatic summary
* Prepare an outline for the meeting to speed things up
<pre><nowiki>
#startmeeting telemetry
#topic some action from previous meeting
#topic something interesting
#topic Open discussion
#endmeeting
</nowiki></pre>

* Update == Agenda for next meeting ==
* Mail the automatic summary as a reply to the invitation

Telemetry/RoadMap

2016-04-28T19:48:26Z

Gordon chung: /* Ceilometer (data collection) */

= Road Map =

Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* adopt oslo.db pagination
* mongo/hbase to sql backend convertor tool
* fix services to use python-aodhclient rather than python-ceilometerclient.

=== Ceilometer (data collection) ===
* add elasticsearch functional gate
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* refine polling
** global caching between pollsters (https://etherpad.openstack.org/p/mitaka-telemetry-polling)
* Cache everything everywhere, all the time
** add to sql driver
* generic notification agent
* rally tests

=== Gnocchi (metric storage) ===
* indexer sharding support
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* project defined meters - leveraging declarative meters
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
* Nova
** the end of nova polling (http://lists.openstack.org/pipermail/openstack-dev/2015-June/067589.html)
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in ceilometer and aodh
* Release to PyPI
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2016-04-28T19:47:19Z

Gordon chung: /* Gnocchi (metric storage) */

= Road Map =

Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* adopt oslo.db pagination
* mongo/hbase to sql backend convertor tool
* fix services to use python-aodhclient rather than python-ceilometerclient.

=== Ceilometer (data collection) ===
* add elasticsearch functional gate
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* refine polling
** global caching between pollsters (https://etherpad.openstack.org/p/mitaka-telemetry-polling)
* Cache everything everywhere, all the time
** add to sql driver
* rally tests

=== Gnocchi (metric storage) ===
* indexer sharding support
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* project defined meters - leveraging declarative meters
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
* Nova
** the end of nova polling (http://lists.openstack.org/pipermail/openstack-dev/2015-June/067589.html)
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in ceilometer and aodh
* Release to PyPI
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Meetings/Telemetry

2016-03-17T13:49:39Z

Gordon chung: /* Agenda */

= Mid-Cycles =

The telemetry team will not hold a midcycle for Mitaka. A virtual one will be discussed for January if required.

Past Midcycles

* [[Meetings/Ceilometer/Liberty Virtual Mid-Cycle|Liberty Virtual Mid-Cycle]]

= Weekly Telemetry meeting =
The telemetry project team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code>:
* '''every''' week on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].

[https://www.google.com/calendar/ical/h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com/public/basic.ics ICAL link for the meeting schedule]

[https://www.google.com/calendar/embed?src=h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com&ctz=UTC HTML view of schedule in UTC]

Everyone is welcome.

The blueprints that are used as a basis for the telemetry project can be found [https://blueprints.launchpad.net/ceilometer here]. We are currently sharing the ceilometer space until aodh and gnocchi requirements warrant segregated management. For now, to ensure collaboration, the space will remain shared.

The process of proposing a new blueprint from Juno onwards is described [https://wiki.openstack.org/wiki/Blueprints#Blueprints_and_Specs here].

=== Agenda ===

'''Please add your name with the agenda item, so we know who to call on during the meeting.'''
* release candidate blockers
* summit planning
** https://etherpad.openstack.org/p/newton-telemetry-summit-planning
** http://lists.openstack.org/pipermail/openstack-dev/2016-March/089467.html
* recurring: roadmap items (new/old/blockers) https://wiki.openstack.org/wiki/Telemetry/RoadMap
* aodh topics
* ceilometer topics
* gnocchi topics
* Open discussion

=== Apologies for absence ===

== Previous meetings ==
* [http://eavesdrop.openstack.org/meetings/telemetry/2016 2016]
* [http://eavesdrop.openstack.org/meetings/telemetry/2015 2015]

=== HIstorical Ceilometer meetings ===
* [http://eavesdrop.openstack.org/meetings/ceilometer/2015 2015]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2014 2014]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2013 2013]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2012 2012]

=== Historical pre-Ceilometer meetings ===
* meeting 16 | 16 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.html summary]
* meeting 15 | 09 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.html summary]
* meeting 14 | 02 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.html summary]
* meeting 13 | 26 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.html summary]
* meeting 12 | 19 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.html summary]
* meeting 11 | 12 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.log.html log]
* meeting 10 | 05 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.log.html log]
* meeting 9 | 28 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.log.html log]
* meeting 8 | 21 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.log.html log]
* meeting 7 | 13 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.log.html log]
* meeting 6 | 7 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.log.html log]
* meeting 5 | 31 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.log.html log]
* meeting 4 | 24 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.log.html log]
* meeting 3 | 17 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.log.html log]
* meeting 2 | 10 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html log]
* meeting 1 | 3 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.log.html log]
* meeting 0 | 26 apr 12 | [[Meetings/MeteringAgenda/meeting-0-summary|summary]] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.log.html log]

== Meeting organizers ==
* Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
* Use http://meetbot.debian.net/Manual.html to get an automatic summary
* Prepare an outline for the meeting to speed things up
<pre><nowiki>
#startmeeting telemetry
#topic some action from previous meeting
#topic something interesting
#topic Open discussion
#endmeeting
</nowiki></pre>

* Update == Agenda for next meeting ==
* Mail the automatic summary as a reply to the invitation

Telemetry

2016-02-29T20:38:51Z

Gordon chung: /* Managed */

= OpenStack Telemetry =

== Project Mission ==
To reliably collect data on the utilization of the physical and virtual resources comprising deployed clouds, persist these data for subsequent retrieval and analysis, and trigger actions when defined criteria are met.

== Services ==
The telemetry requirements of an OpenStack environment are vast and varied, they include use cases such as metering, monitoring, and alarming to name a few. The scope of these uses cases are diverse and beyond the scope of a single project and team. Currently, the telemetry project provides a set of functionality split across multiple projects; each project designed to provide a discrete service in the telemetry space.

=== Managed ===
The current set of projects are managed by the telemetry team are:
* [https://github.com/openstack/aodh Aodh] - an alarming service
* [https://github.com/openstack/ceilometer Ceilometer] - a data collection service
* [https://github.com/openstack/gnocchi Gnocchi] - a time-series database and resource indexing service

{| border="1" cellpadding="2" cellspacing="0"
| Specs
| https://github.com/openstack/ceilometer-specs
|-
| Admin doc
| http://docs.openstack.org/admin-guide-cloud/telemetry.html
|-
| Meetings
| https://wiki.openstack.org/wiki/Meetings/Telemetry
|}

Currently, a common spec repo and meeting time are shared between all managed projects

==== Aodh ====
* team lead - Liusheng (liusheng)
Aodh's goal is to enable the ability to trigger actions based on defined rules against sample or event data collected by Ceilometer

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/aodh
|-
| Blueprints
| https://blueprints.launchpad.net/aodh
|-
| Bug tracker
| https://bugs.launchpad.net/aodh
|-
| Developer doc
| http://docs.openstack.org/developer/aodh/
|-
| Tarballs
| http://tarballs.openstack.org/aodh/
|}

==== Ceilometer ====
* team lead - Gordon Chung (gordc)
Ceilometer's goal is to efficiently collect, normalise and transform data produced by OpenStack services. The data it collects is intended to be used to create different views and help solve various telemetry use cases. Aodh and Gnocchi are two examples of services extending Ceilometer data.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/ceilometer
|-
| Blueprints
| https://blueprints.launchpad.net/ceilometer
|-
| Bug tracker
| https://bugs.launchpad.net/ceilometer
|-
| Developer doc
| http://docs.openstack.org/developer/ceilometer/
|-
| Tarballs
| http://tarballs.openstack.org/ceilometer/
|}

==== Gnocchi ====
* team lead - Julien Danjou (jd__)
Gnocchi's goal is to provide a time-series resource indexing, metric storage service which enables users to capture OpenStack resources and the metrics associated with them. Using rolling aggregation set by user-defined archival policies, it's aim is to provide a scalable means of storing both short and long term data and provide a statistical view based on the input data (ie. Ceilometer)

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/gnocchi
|-
| Bug tracker
| https://bugs.launchpad.net/gnocchi
|-
| Developer doc
| http://docs.openstack.org/developer/gnocchi/
|-
| Tarballs
| http://tarballs.openstack.org/gnocchi/
|}

=== Externally Managed ===
* [https://github.com/openstack/heat Heat] - Orchestration service which provides autoscaling capabilities using Ceilometer data.
* [https://github.com/openstack/horizon Horizon] - UI service which allows interaction with Aodh data.
* [https://github.com/stackforge/ceilometer-powervm PowerVM] - PowerVM pollster plugin. Owners: thorst and efried. IRC: #openstack-powervm
* [https://github.com/stackforge/cloudkitty CloudKitty] - OpenStack Rating as a Service component and usage reporting.
* [https://github.com/spilgames/ceilometer_graphite_publisher Graphite Publisher] - Ceilometer publisher to connect to Graphite.
* [https://github.com/openstack/watcher Watcher] - Resource optimization service.
* [http://icclab.github.io/cyclops Cyclops] - Rating-Charging-Billing Solution for Cloud providers.
* [https://github.com/openstack/collectd-ceilometer-plugin Collectd] - A Collectd writer plugin to publish telemetry to Ceilometer.

== Road Map ==
The future direction and plans of the project can be found [[Telemetry/RoadMap|here]]. Feel free to pick up a task if something interests you. Anyone is free to propose their own ideas in a spec as well.

== Contributing to Telemetry ==
The developer documentation can be found in each projects respective documentation page.

The telemetry project team hangs out on Freenode in the #openstack-telemetry channel, feel free to drop by and stay as long as you want. We use the [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Developers List] for our email discussions. If you want to make a post relevant to multiple projects in telemetry space,
please tag the subject with [telemetry]. If you have a post regarding a single project, please tag the subject with the appropriate tag: [aodh], [ceilometer] or [gnocchi].

The project team officially meets once a week, see [[Meetings/Telemetry]].

[[Category:Telemetry]]

Meetings/Telemetry

2016-02-18T16:37:25Z

Gordon chung: /* Weekly Telemetry meeting */

= Mid-Cycles =

The telemetry team will not hold a midcycle for Mitaka. A virtual one will be discussed for January if required.

Past Midcycles

* [[Meetings/Ceilometer/Liberty Virtual Mid-Cycle|Liberty Virtual Mid-Cycle]]

= Weekly Telemetry meeting =
The telemetry project team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code>:
* '''every''' week on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].

[https://www.google.com/calendar/ical/h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com/public/basic.ics ICAL link for the meeting schedule]

[https://www.google.com/calendar/embed?src=h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com&ctz=UTC HTML view of schedule in UTC]

Everyone is welcome.

The blueprints that are used as a basis for the telemetry project can be found [https://blueprints.launchpad.net/ceilometer here]. We are currently sharing the ceilometer space until aodh and gnocchi requirements warrant segregated management. For now, to ensure collaboration, the space will remain shared.

The process of proposing a new blueprint from Juno onwards is described [https://wiki.openstack.org/wiki/Blueprints#Blueprints_and_Specs here].

=== Agenda ===

'''Please add your name with the agenda item, so we know who to call on during the meeting.'''
* recurring: roadmap items (new/old/blockers) https://wiki.openstack.org/wiki/Telemetry/RoadMap
* aodh topics
* ceilometer topics
* gnocchi topics
* Open discussion

=== Apologies for absence ===

== Previous meetings ==
* [http://eavesdrop.openstack.org/meetings/telemetry/2016 2016]
* [http://eavesdrop.openstack.org/meetings/telemetry/2015 2015]

=== HIstorical Ceilometer meetings ===
* [http://eavesdrop.openstack.org/meetings/ceilometer/2015 2015]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2014 2014]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2013 2013]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2012 2012]

=== Historical pre-Ceilometer meetings ===
* meeting 16 | 16 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.html summary]
* meeting 15 | 09 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.html summary]
* meeting 14 | 02 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.html summary]
* meeting 13 | 26 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.html summary]
* meeting 12 | 19 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.html summary]
* meeting 11 | 12 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.log.html log]
* meeting 10 | 05 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.log.html log]
* meeting 9 | 28 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.log.html log]
* meeting 8 | 21 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.log.html log]
* meeting 7 | 13 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.log.html log]
* meeting 6 | 7 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.log.html log]
* meeting 5 | 31 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.log.html log]
* meeting 4 | 24 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.log.html log]
* meeting 3 | 17 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.log.html log]
* meeting 2 | 10 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html log]
* meeting 1 | 3 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.log.html log]
* meeting 0 | 26 apr 12 | [[Meetings/MeteringAgenda/meeting-0-summary|summary]] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.log.html log]

== Meeting organizers ==
* Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
* Use http://meetbot.debian.net/Manual.html to get an automatic summary
* Prepare an outline for the meeting to speed things up
<pre><nowiki>
#startmeeting telemetry
#topic some action from previous meeting
#topic something interesting
#topic Open discussion
#endmeeting
</nowiki></pre>

* Update == Agenda for next meeting ==
* Mail the automatic summary as a reply to the invitation

Telemetry

2016-02-04T16:09:38Z

Gordon chung: /* Aodh */

= OpenStack Telemetry =

== Project Mission ==
To reliably collect data on the utilization of the physical and virtual resources comprising deployed clouds, persist these data for subsequent retrieval and analysis, and trigger actions when defined criteria are met.

== Services ==
The telemetry requirements of an OpenStack environment are vast and varied, they include use cases such as metering, monitoring, and alarming to name a few. The scope of these uses cases are diverse and beyond the scope of a single project and team. Currently, the telemetry project provides a set of functionality split across multiple projects; each project designed to provide a discrete service in the telemetry space.

=== Managed ===
The current set of projects are managed by the telemetry team are:
* [https://github.com/openstack/aodh Aodh] - an alarming service
* [https://github.com/openstack/ceilometer Ceilometer] - a data collection service
* [https://github.com/openstack/gnocchi Gnocchi] - a time-series database and resource indexing service

{| border="1" cellpadding="2" cellspacing="0"
| Specs
| https://github.com/openstack/ceilometer-specs
|-
| Blueprints
| https://blueprints.launchpad.net/ceilometer
|-
| Admin doc
| http://docs.openstack.org/admin-guide-cloud/telemetry.html
|-
| Meetings
| https://wiki.openstack.org/wiki/Meetings/Telemetry
|}

Currently, a common spec repo and meeting time are shared between all managed projects

==== Aodh ====
* team lead - Liusheng (liusheng)
Aodh's goal is to enable the ability to trigger actions based on defined rules against sample or event data collected by Ceilometer

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/aodh
|-
| Bug tracker
| https://bugs.launchpad.net/aodh
|-
| Developer doc
| http://docs.openstack.org/developer/aodh/
|-
| Tarballs
| http://tarballs.openstack.org/aodh/
|}

==== Ceilometer ====
* team lead - Gordon Chung (gordc)
Ceilometer's goal is to efficiently collect, normalise and transform data produced by OpenStack services. The data it collects is intended to be used to create different views and help solve various telemetry use cases. Aodh and Gnocchi are two examples of services extending Ceilometer data.

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/ceilometer
|-
| Bug tracker
| https://bugs.launchpad.net/ceilometer
|-
| Developer doc
| http://docs.openstack.org/developer/ceilometer/
|-
| Tarballs
| http://tarballs.openstack.org/ceilometer/
|}

==== Gnocchi ====
* team lead - Julien Danjou (jd__)
Gnocchi's goal is to provide a time-series resource indexing, metric storage service which enables users to capture OpenStack resources and the metrics associated with them. Using rolling aggregation set by user-defined archival policies, it's aim is to provide a scalable means of storing both short and long term data and provide a statistical view based on the input data (ie. Ceilometer)

{| border="1" cellpadding="2" cellspacing="0"
| Source code
| https://github.com/openstack/gnocchi
|-
| Bug tracker
| https://bugs.launchpad.net/gnocchi
|-
| Developer doc
| http://docs.openstack.org/developer/gnocchi/
|-
| Tarballs
| http://tarballs.openstack.org/gnocchi/
|}

=== Externally Managed ===
* [https://github.com/openstack/heat Heat] - Orchestration service which provides autoscaling capabilities using Ceilometer data.
* [https://github.com/openstack/horizon Horizon] - UI service which allows interaction with Aodh data.
* [https://github.com/stackforge/ceilometer-powervm PowerVM] - PowerVM pollster plugin. Owners: thorst and efried. IRC: #openstack-powervm
* [https://github.com/stackforge/cloudkitty CloudKitty] - OpenStack Rating as a Service component and usage reporting.
* [https://github.com/spilgames/ceilometer_graphite_publisher Graphite Publisher] - Ceilometer publisher to connect to Graphite.
* [https://github.com/openstack/watcher Watcher] - Resource optimization service.
* [http://icclab.github.io/cyclops Cyclops] - Rating-Charging-Billing Solution for Cloud providers.
* [https://github.com/openstack/collectd-ceilometer-plugin Collectd] - A Collectd writer plugin to publish telemetry to Ceilometer.

== Road Map ==
The future direction and plans of the project can be found [[Telemetry/RoadMap|here]]. Feel free to pick up a task if something interests you. Anyone is free to propose their own ideas in a spec as well.

== Contributing to Telemetry ==
The developer documentation can be found in each projects respective documentation page.

The telemetry project team hangs out on Freenode in the #openstack-telemetry channel, feel free to drop by and stay as long as you want. We use the [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Developers List] for our email discussions. If you want to make a post relevant to multiple projects in telemetry space,
please tag the subject with [telemetry]. If you have a post regarding a single project, please tag the subject with the appropriate tag: [aodh], [ceilometer] or [gnocchi].

The project team officially meets once a week, see [[Meetings/Telemetry]].

[[Category:Telemetry]]

Telemetry/RoadMap

2016-01-28T15:28:54Z

Gordon chung: /* Open Work Items */

= Road Map =

Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. If a new resource is found, the following will happen; if not, it might take a while.

For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* adopt oslo.db pagination
* mongo/hbase to sql backend convertor tool
* fix services to use python-aodhclient rather than python-ceilometerclient.

=== Ceilometer (data collection) ===
* add elasticsearch functional gate
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* refine polling
** global caching between pollsters (https://etherpad.openstack.org/p/mitaka-telemetry-polling)
* Cache everything everywhere, all the time
** add to sql driver
* rally tests

=== Gnocchi (metric storage) ===
* indexer sharding support
* dynamic resource creation
* benchmark
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* project defined meters - leveraging declarative meters
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
* Nova
** the end of nova polling (http://lists.openstack.org/pipermail/openstack-dev/2015-June/067589.html)
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in ceilometer and aodh
* Release to PyPI
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2016-01-28T15:26:34Z

Gordon chung: /* Aodh (alarming) */

= Road Map =

Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener
* adopt oslo.db pagination
* mongo/hbase to sql backend convertor tool
* fix services to use python-aodhclient rather than python-ceilometerclient.

=== Ceilometer (data collection) ===
* add elasticsearch functional gate
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* refine polling
** global caching between pollsters (https://etherpad.openstack.org/p/mitaka-telemetry-polling)
* Cache everything everywhere, all the time
** add to sql driver
* rally tests

=== Gnocchi (metric storage) ===
* indexer sharding support
* dynamic resource creation
* benchmark
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* project defined meters - leveraging declarative meters
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
* Nova
** the end of nova polling (http://lists.openstack.org/pipermail/openstack-dev/2015-June/067589.html)
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in ceilometer and aodh
* Release to PyPI
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2016-01-25T14:20:37Z

Gordon chung: /* Future Targets */

= Road Map =

Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener

=== Ceilometer (data collection) ===
* add elasticsearch functional gate
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* refine polling
** global caching between pollsters (https://etherpad.openstack.org/p/mitaka-telemetry-polling)
* Cache everything everywhere, all the time
** add to sql driver
* rally tests

=== Gnocchi (metric storage) ===
* indexer sharding support
* dynamic resource creation
* benchmark
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* project defined meters - leveraging declarative meters
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
* Nova
** the end of nova polling (http://lists.openstack.org/pipermail/openstack-dev/2015-June/067589.html)
** nova cell metrics
** nova availability zone metrics
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in ceilometer and aodh
* Release to PyPI
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2016-01-25T14:18:54Z

Gordon chung: /* Aodh (alarming) */

= Road Map =

Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests
* event alarm multiple workers
* use oslo.messaging batch notification listener

=== Ceilometer (data collection) ===
* add elasticsearch functional gate
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* refine polling
** global caching between pollsters (https://etherpad.openstack.org/p/mitaka-telemetry-polling)
* Cache everything everywhere, all the time
** add to sql driver
* rally tests

=== Gnocchi (metric storage) ===
* indexer sharding support
* dynamic resource creation
* benchmark
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* project defined meters - leveraging declarative meters
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
* Nova
** the end of nova polling (http://lists.openstack.org/pipermail/openstack-dev/2015-June/067589.html)
** nova cell metrics
** nova availability zone metrics
* batching support for recording of event and meter data
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in ceilometer and aodh
* Release to PyPI
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2016-01-25T14:18:41Z

Gordon chung: /* Ceilometer (data collection) */

= Road Map =

Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests
* event alarm multiple workers
* batch listener.

=== Ceilometer (data collection) ===
* add elasticsearch functional gate
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* refine polling
** global caching between pollsters (https://etherpad.openstack.org/p/mitaka-telemetry-polling)
* Cache everything everywhere, all the time
** add to sql driver
* rally tests

=== Gnocchi (metric storage) ===
* indexer sharding support
* dynamic resource creation
* benchmark
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* project defined meters - leveraging declarative meters
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
* Nova
** the end of nova polling (http://lists.openstack.org/pipermail/openstack-dev/2015-June/067589.html)
** nova cell metrics
** nova availability zone metrics
* batching support for recording of event and meter data
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in ceilometer and aodh
* Release to PyPI
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2016-01-25T14:18:27Z

Gordon chung: /* Aodh (alarming) */

= Road Map =

Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests
* event alarm multiple workers
* batch listener.

=== Ceilometer (data collection) ===
* add elasticsearch functional gate
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* refine polling
** global caching between pollsters (https://etherpad.openstack.org/p/mitaka-telemetry-polling)
* Cache everything everywhere, all the time
** add to sql driver
* rally tests
* use oslo.messaging batch notification listener

=== Gnocchi (metric storage) ===
* indexer sharding support
* dynamic resource creation
* benchmark
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* project defined meters - leveraging declarative meters
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
* Nova
** the end of nova polling (http://lists.openstack.org/pipermail/openstack-dev/2015-June/067589.html)
** nova cell metrics
** nova availability zone metrics
* batching support for recording of event and meter data
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in ceilometer and aodh
* Release to PyPI
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Meetings/Telemetry

2016-01-08T22:16:02Z

Gordon chung: /* Agenda */

= Mid-Cycles =

The telemetry team will not hold a midcycle for Mitaka. A virtual one will be discussed for January if required.

Past Midcycles

* [[Meetings/Ceilometer/Liberty Virtual Mid-Cycle|Liberty Virtual Mid-Cycle]]

= Weekly Telemetry meeting =
The telemetry project team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code>:
* '''every''' week on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].

[https://www.google.com/calendar/ical/h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com/public/basic.ics ICAL link for the meeting schedule]

[https://www.google.com/calendar/embed?src=h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com&ctz=UTC HTML view of schedule in UTC]

Everyone is welcome.

The blueprints that are used as a basis for the telemetry project can be found [https://blueprints.launchpad.net/ceilometer here]. We are currently sharing the ceilometer space until aodh and gnocchi requirements warrant segregated management. For now, to ensure collaboration, the space will remain shared.

The process of proposing a new blueprint from Juno onwards is described [https://wiki.openstack.org/wiki/Blueprints#Blueprints_and_Specs here].

=== Agenda ===

'''Please add your name with the agenda item, so we know who to call on during the meeting.'''
* recurring: roadmap items (new/old/blockers) https://wiki.openstack.org/wiki/Telemetry/RoadMap
* aodh topics
* ceilometer topics
* gnocchi topics
* Open discussion

=== Apologies for absence ===
*

== Previous meetings ==
* [http://eavesdrop.openstack.org/meetings/telemetry/2016 2016]
* [http://eavesdrop.openstack.org/meetings/telemetry/2015 2015]

=== HIstorical Ceilometer meetings ===
* [http://eavesdrop.openstack.org/meetings/ceilometer/2015 2015]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2014 2014]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2013 2013]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2012 2012]

=== Historical pre-Ceilometer meetings ===
* meeting 16 | 16 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.html summary]
* meeting 15 | 09 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.html summary]
* meeting 14 | 02 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.html summary]
* meeting 13 | 26 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.html summary]
* meeting 12 | 19 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.html summary]
* meeting 11 | 12 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.log.html log]
* meeting 10 | 05 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.log.html log]
* meeting 9 | 28 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.log.html log]
* meeting 8 | 21 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.log.html log]
* meeting 7 | 13 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.log.html log]
* meeting 6 | 7 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.log.html log]
* meeting 5 | 31 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.log.html log]
* meeting 4 | 24 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.log.html log]
* meeting 3 | 17 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.log.html log]
* meeting 2 | 10 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html log]
* meeting 1 | 3 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.log.html log]
* meeting 0 | 26 apr 12 | [[Meetings/MeteringAgenda/meeting-0-summary|summary]] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.log.html log]

== Meeting organizers ==
* Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
* Use http://meetbot.debian.net/Manual.html to get an automatic summary
* Prepare an outline for the meeting to speed things up
<pre><nowiki>
#startmeeting telemetry
#topic some action from previous meeting
#topic something interesting
#topic Open discussion
#endmeeting
</nowiki></pre>

* Update == Agenda for next meeting ==
* Mail the automatic summary as a reply to the invitation

Meetings/Telemetry

2016-01-08T22:15:51Z

Gordon chung: /* Previous meetings */

= Mid-Cycles =

The telemetry team will not hold a midcycle for Mitaka. A virtual one will be discussed for January if required.

Past Midcycles

* [[Meetings/Ceilometer/Liberty Virtual Mid-Cycle|Liberty Virtual Mid-Cycle]]

= Weekly Telemetry meeting =
The telemetry project team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code>:
* '''every''' week on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].

[https://www.google.com/calendar/ical/h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com/public/basic.ics ICAL link for the meeting schedule]

[https://www.google.com/calendar/embed?src=h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com&ctz=UTC HTML view of schedule in UTC]

Everyone is welcome.

The blueprints that are used as a basis for the telemetry project can be found [https://blueprints.launchpad.net/ceilometer here]. We are currently sharing the ceilometer space until aodh and gnocchi requirements warrant segregated management. For now, to ensure collaboration, the space will remain shared.

The process of proposing a new blueprint from Juno onwards is described [https://wiki.openstack.org/wiki/Blueprints#Blueprints_and_Specs here].

=== Agenda ===

'''Please add your name with the agenda item, so we know who to call on during the meeting.'''
* recurring: roadmap items (new/old/blockers) https://wiki.openstack.org/wiki/Telemetry/RoadMap
* virtual midcycle?
* aodh topics
** how to represent gnocchi alarms in client
* ceilometer topics
* gnocchi topics
* Open discussion

=== Apologies for absence ===
*

== Previous meetings ==
* [http://eavesdrop.openstack.org/meetings/telemetry/2016 2016]
* [http://eavesdrop.openstack.org/meetings/telemetry/2015 2015]

=== HIstorical Ceilometer meetings ===
* [http://eavesdrop.openstack.org/meetings/ceilometer/2015 2015]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2014 2014]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2013 2013]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2012 2012]

=== Historical pre-Ceilometer meetings ===
* meeting 16 | 16 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.html summary]
* meeting 15 | 09 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.html summary]
* meeting 14 | 02 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.html summary]
* meeting 13 | 26 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.html summary]
* meeting 12 | 19 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.html summary]
* meeting 11 | 12 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.log.html log]
* meeting 10 | 05 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.log.html log]
* meeting 9 | 28 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.log.html log]
* meeting 8 | 21 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.log.html log]
* meeting 7 | 13 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.log.html log]
* meeting 6 | 7 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.log.html log]
* meeting 5 | 31 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.log.html log]
* meeting 4 | 24 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.log.html log]
* meeting 3 | 17 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.log.html log]
* meeting 2 | 10 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html log]
* meeting 1 | 3 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.log.html log]
* meeting 0 | 26 apr 12 | [[Meetings/MeteringAgenda/meeting-0-summary|summary]] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.log.html log]

== Meeting organizers ==
* Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
* Use http://meetbot.debian.net/Manual.html to get an automatic summary
* Prepare an outline for the meeting to speed things up
<pre><nowiki>
#startmeeting telemetry
#topic some action from previous meeting
#topic something interesting
#topic Open discussion
#endmeeting
</nowiki></pre>

* Update == Agenda for next meeting ==
* Mail the automatic summary as a reply to the invitation

Meetings/Telemetry

2016-01-07T14:59:32Z

Gordon chung: /* Agenda */

= Mid-Cycles =

The telemetry team will not hold a midcycle for Mitaka. A virtual one will be discussed for January if required.

Past Midcycles

* [[Meetings/Ceilometer/Liberty Virtual Mid-Cycle|Liberty Virtual Mid-Cycle]]

= Weekly Telemetry meeting =
The telemetry project team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code>:
* '''every''' week on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].

[https://www.google.com/calendar/ical/h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com/public/basic.ics ICAL link for the meeting schedule]

[https://www.google.com/calendar/embed?src=h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com&ctz=UTC HTML view of schedule in UTC]

Everyone is welcome.

The blueprints that are used as a basis for the telemetry project can be found [https://blueprints.launchpad.net/ceilometer here]. We are currently sharing the ceilometer space until aodh and gnocchi requirements warrant segregated management. For now, to ensure collaboration, the space will remain shared.

The process of proposing a new blueprint from Juno onwards is described [https://wiki.openstack.org/wiki/Blueprints#Blueprints_and_Specs here].

=== Agenda ===

'''Please add your name with the agenda item, so we know who to call on during the meeting.'''
* recurring: roadmap items (new/old/blockers) https://wiki.openstack.org/wiki/Telemetry/RoadMap
* virtual midcycle?
* aodh topics
** how to represent gnocchi alarms in client
* ceilometer topics
* gnocchi topics
* Open discussion

=== Apologies for absence ===
*

== Previous meetings ==
* [http://eavesdrop.openstack.org/meetings/telemetry/2015 2015]

=== HIstorical Ceilometer meetings ===
* [http://eavesdrop.openstack.org/meetings/ceilometer/2015 2015]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2014 2014]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2013 2013]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2012 2012]

=== Historical pre-Ceilometer meetings ===
* meeting 16 | 16 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.html summary]
* meeting 15 | 09 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.html summary]
* meeting 14 | 02 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.html summary]
* meeting 13 | 26 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.html summary]
* meeting 12 | 19 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.html summary]
* meeting 11 | 12 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.log.html log]
* meeting 10 | 05 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.log.html log]
* meeting 9 | 28 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.log.html log]
* meeting 8 | 21 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.log.html log]
* meeting 7 | 13 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.log.html log]
* meeting 6 | 7 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.log.html log]
* meeting 5 | 31 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.log.html log]
* meeting 4 | 24 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.log.html log]
* meeting 3 | 17 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.log.html log]
* meeting 2 | 10 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html log]
* meeting 1 | 3 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.log.html log]
* meeting 0 | 26 apr 12 | [[Meetings/MeteringAgenda/meeting-0-summary|summary]] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.log.html log]

== Meeting organizers ==
* Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
* Use http://meetbot.debian.net/Manual.html to get an automatic summary
* Prepare an outline for the meeting to speed things up
<pre><nowiki>
#startmeeting telemetry
#topic some action from previous meeting
#topic something interesting
#topic Open discussion
#endmeeting
</nowiki></pre>

* Update == Agenda for next meeting ==
* Mail the automatic summary as a reply to the invitation

Meetings/Telemetry

2016-01-07T12:43:26Z

Gordon chung: /* Agenda */

= Mid-Cycles =

The telemetry team will not hold a midcycle for Mitaka. A virtual one will be discussed for January if required.

Past Midcycles

* [[Meetings/Ceilometer/Liberty Virtual Mid-Cycle|Liberty Virtual Mid-Cycle]]

= Weekly Telemetry meeting =
The telemetry project team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code>:
* '''every''' week on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].

[https://www.google.com/calendar/ical/h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com/public/basic.ics ICAL link for the meeting schedule]

[https://www.google.com/calendar/embed?src=h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com&ctz=UTC HTML view of schedule in UTC]

Everyone is welcome.

The blueprints that are used as a basis for the telemetry project can be found [https://blueprints.launchpad.net/ceilometer here]. We are currently sharing the ceilometer space until aodh and gnocchi requirements warrant segregated management. For now, to ensure collaboration, the space will remain shared.

The process of proposing a new blueprint from Juno onwards is described [https://wiki.openstack.org/wiki/Blueprints#Blueprints_and_Specs here].

=== Agenda ===

'''Please add your name with the agenda item, so we know who to call on during the meeting.'''
* recurring: roadmap items (new/old/blockers) https://wiki.openstack.org/wiki/Telemetry/RoadMap
* virtual midcycle?
* aodh topics
* ceilometer topics
* gnocchi topics
* Open discussion

=== Apologies for absence ===
*

== Previous meetings ==
* [http://eavesdrop.openstack.org/meetings/telemetry/2015 2015]

=== HIstorical Ceilometer meetings ===
* [http://eavesdrop.openstack.org/meetings/ceilometer/2015 2015]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2014 2014]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2013 2013]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2012 2012]

=== Historical pre-Ceilometer meetings ===
* meeting 16 | 16 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.html summary]
* meeting 15 | 09 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.html summary]
* meeting 14 | 02 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.html summary]
* meeting 13 | 26 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.html summary]
* meeting 12 | 19 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.html summary]
* meeting 11 | 12 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.log.html log]
* meeting 10 | 05 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.log.html log]
* meeting 9 | 28 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.log.html log]
* meeting 8 | 21 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.log.html log]
* meeting 7 | 13 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.log.html log]
* meeting 6 | 7 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.log.html log]
* meeting 5 | 31 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.log.html log]
* meeting 4 | 24 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.log.html log]
* meeting 3 | 17 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.log.html log]
* meeting 2 | 10 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html log]
* meeting 1 | 3 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.log.html log]
* meeting 0 | 26 apr 12 | [[Meetings/MeteringAgenda/meeting-0-summary|summary]] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.log.html log]

== Meeting organizers ==
* Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
* Use http://meetbot.debian.net/Manual.html to get an automatic summary
* Prepare an outline for the meeting to speed things up
<pre><nowiki>
#startmeeting telemetry
#topic some action from previous meeting
#topic something interesting
#topic Open discussion
#endmeeting
</nowiki></pre>

* Update == Agenda for next meeting ==
* Mail the automatic summary as a reply to the invitation

Telemetry/RoadMap

2015-12-15T14:03:31Z

Gordon chung: /* Ceilometer (data collection) */

= Road Map =

Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests

=== Ceilometer (data collection) ===
* add elasticsearch functional gate
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* refine polling
** global caching between pollsters (https://etherpad.openstack.org/p/mitaka-telemetry-polling)
* Cache everything everywhere, all the time
** add to sql driver
* rally tests
* use oslo.messaging batch notification listener

=== Gnocchi (metric storage) ===
* indexer sharding support
* dynamic resource creation
* benchmark
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* project defined meters - leveraging declarative meters
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
* Nova
** the end of nova polling (http://lists.openstack.org/pipermail/openstack-dev/2015-June/067589.html)
** nova cell metrics
** nova availability zone metrics
* batching support for recording of event and meter data
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in ceilometer and aodh
* Release to PyPI
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2015-12-15T14:02:58Z

Gordon chung: /* Aodh (alarming) */

= Road Map =

Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests

=== Ceilometer (data collection) ===
* add elasticsearch functional gate
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* refine polling
** global caching between pollsters (https://etherpad.openstack.org/p/mitaka-telemetry-polling)
* Cache everything everywhere, all the time
** in particular dogpile.cache (because it is already used in Keystone) in the gnocchi dispatcher in ceilometer to cache resources (see [https://review.openstack.org/#/c/203109/ POC])
** add to sql driver
* rally tests
* migrate tempest plugin
* use oslo.messaging batch notification listener

=== Gnocchi (metric storage) ===
* indexer sharding support
* dynamic resource creation
* benchmark
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* project defined meters - leveraging declarative meters
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
* Nova
** the end of nova polling (http://lists.openstack.org/pipermail/openstack-dev/2015-June/067589.html)
** nova cell metrics
** nova availability zone metrics
* batching support for recording of event and meter data
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in ceilometer and aodh
* Release to PyPI
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Telemetry/RoadMap

2015-12-10T15:02:17Z

Gordon chung: /* Ceilometer (data collection) */

= Road Map =

Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka

* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
* pre-existing blueprints - https://blueprints.launchpad.net/ceilometer

== Priority Work Items ==
The following are high priority items targeted for the current cycle that require owners:

== Open Work Items ==
The following is a list of work items that have been approved conceptually and can be targeted for the current development cycle. For more information on a item, contact us on openstack-dev mailing list or on freenode at #openstack-telemetry. The current list of core contributors can be found at each projects respective page:
* https://launchpad.net/~aodh-drivers/+members#active
* https://launchpad.net/~ceilometer-drivers/+members#active
* https://launchpad.net/~gnocchi-drivers/+members#active

=== Aodh (alarming) ===
* in-tree functional tests
* new aodhclient
** based on gnocchiclient to ensure we use latest and greatest.
** syntax needs to be simplified, too many options.
* migrate tempest plugin

=== Ceilometer (data collection) ===
* add elasticsearch functional gate
* Polling schema - separate polling logic from pipeline
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
* refine polling
** global caching between pollsters (https://etherpad.openstack.org/p/mitaka-telemetry-polling)
* Cache everything everywhere, all the time
** in particular dogpile.cache (because it is already used in Keystone) in the gnocchi dispatcher in ceilometer to cache resources (see [https://review.openstack.org/#/c/203109/ POC])
** add to sql driver
* rally tests
* migrate tempest plugin
* use oslo.messaging batch notification listener

=== Gnocchi (metric storage) ===
* indexer sharding support
* dynamic resource creation
* benchmark
* migrate tempest plugin

== Future Targets ==
These ideas have been discussed/introduced at a high-level. They are areas of interests for the users/developers of Ceilometer but still require discussion. Proposals for concrete work items related to these items are welcomed for future cycles:

* log processing
* application level monitoring
* project defined meters - leveraging declarative meters
* group based configuration control - connect tooz to manage configuration and allow for better control of configuration updates.
* Nova
** the end of nova polling (http://lists.openstack.org/pipermail/openstack-dev/2015-June/067589.html)
** nova cell metrics
** nova availability zone metrics
* batching support for recording of event and meter data
* project level pipeline control. enable ability to poll at different frequencies per project.
* granular ttl control (project level / meter level)
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in ceilometer and aodh
* Release to PyPI
* Use specific configuration to load selected stevedore extensions, not all of them
** remove stevedore plugins out of tree
* Add more complete evaluation of the upgrade process in the grenade plugin.
* Notification and pollster driven functional/integration tests.

== Past Cycles ==
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Meetings/Telemetry

2015-12-10T14:57:23Z

Gordon chung: /* Agenda */

= Mid-Cycles =

The telemetry team will not hold a midcycle for Mitaka. A virtual one will be discussed for January if required.

Past Midcycles

* [[Meetings/Ceilometer/Liberty Virtual Mid-Cycle|Liberty Virtual Mid-Cycle]]

= Weekly Telemetry meeting =
The telemetry project team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code>:
* '''every''' week on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].

[https://www.google.com/calendar/ical/h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com/public/basic.ics ICAL link for the meeting schedule]

[https://www.google.com/calendar/embed?src=h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com&ctz=UTC HTML view of schedule in UTC]

Everyone is welcome.

The blueprints that are used as a basis for the telemetry project can be found [https://blueprints.launchpad.net/ceilometer here]. We are currently sharing the ceilometer space until aodh and gnocchi requirements warrant segregated management. For now, to ensure collaboration, the space will remain shared.

The process of proposing a new blueprint from Juno onwards is described [https://wiki.openstack.org/wiki/Blueprints#Blueprints_and_Specs here].

=== Agenda ===

'''Please add your name with the agenda item, so we know who to call on during the meeting.'''
* recurring: roadmap items (new/old/blockers) https://wiki.openstack.org/wiki/Telemetry/RoadMap
* aodh topics
* ceilometer topics
* gnocchi topics
* Open discussion

=== Apologies for absence ===
*

== Previous meetings ==
* [http://eavesdrop.openstack.org/meetings/telemetry/2015 2015]

=== HIstorical Ceilometer meetings ===
* [http://eavesdrop.openstack.org/meetings/ceilometer/2015 2015]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2014 2014]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2013 2013]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2012 2012]

=== Historical pre-Ceilometer meetings ===
* meeting 16 | 16 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.html summary]
* meeting 15 | 09 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.html summary]
* meeting 14 | 02 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.html summary]
* meeting 13 | 26 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.html summary]
* meeting 12 | 19 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.html summary]
* meeting 11 | 12 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.log.html log]
* meeting 10 | 05 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.log.html log]
* meeting 9 | 28 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.log.html log]
* meeting 8 | 21 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.log.html log]
* meeting 7 | 13 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.log.html log]
* meeting 6 | 7 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.log.html log]
* meeting 5 | 31 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.log.html log]
* meeting 4 | 24 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.log.html log]
* meeting 3 | 17 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.log.html log]
* meeting 2 | 10 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html log]
* meeting 1 | 3 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.log.html log]
* meeting 0 | 26 apr 12 | [[Meetings/MeteringAgenda/meeting-0-summary|summary]] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.log.html log]

== Meeting organizers ==
* Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
* Use http://meetbot.debian.net/Manual.html to get an automatic summary
* Prepare an outline for the meeting to speed things up
<pre><nowiki>
#startmeeting telemetry
#topic some action from previous meeting
#topic something interesting
#topic Open discussion
#endmeeting
</nowiki></pre>

* Update == Agenda for next meeting ==
* Mail the automatic summary as a reply to the invitation

Meetings/InfraTeamMeeting

2015-11-23T20:25:37Z

Gordon chung: /* Upcoming Project Renames */

{{:Header}}

= Weekly Project Infrastructure team meeting =

The OpenStack Project Infrastructure Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.

Please feel free to add agenda items (and your IRC nick in parenthesis).

== Agenda for next meeting ==

* Announcements
* Actions from last meeting
* Specs approval
** PROPOSED: Add extension to openstackci for next phase of work (phschwartz)
*** https://review.openstack.org/239810
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/dib-nodepool.html Use Diskimage Builder in Nodepool]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/gerrit-2.11.html Gerrit 2.11 Upgrade]
*** [https://etherpad.openstack.org/p/mitaka-infra-gerritdevelopment planning]
*** [https://etherpad.openstack.org/p/test-gerrit-2.11 testing]
*** [https://etherpad.openstack.org/p/gerrit-2.11-upgrade upgrade tasks]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/logs-in-swift.html Store Build Logs in Swift]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/maniphest.html maniphest migration]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
* Open discussion
** [https://review.openstack.org/#/c/248123/ Enable Tempest for Magnum] (dimtruck)
** [http://lists.openstack.org/pipermail/openstack-infra/2015-November/003465.html Translations check website] (pleia2)

== Upcoming Project Renames ==
(any additions should mention original->new full names and link to the corresponding change in Gerrit)

* openstack-attic/akanada -> openstack-attic/akanda (NEEDS GERRIT CHANGE, MANUAL CLEANUP)
** the patch was fine but the gerrit db commands had an error in the name in steps 5, 6 and 8: https://etherpad.openstack.org/p/project-renames-November-6-2015
* openstack/ceilometer-specs -> openstack/telemetry-specs
** rename patch: https://review.openstack.org/248897
** governance: https://review.openstack.org/#/c/240809/

== Previous meetings ==
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/

Meetings/Telemetry

2015-11-19T16:28:59Z

Gordon chung: /* Agenda */

= Mid-Cycles =

The telemetry team will not hold a midcycle for Mitaka. A virtual one will be discussed for January if required.

Past Midcycles

* [[Meetings/Ceilometer/Liberty Virtual Mid-Cycle|Liberty Virtual Mid-Cycle]]

= Weekly Telemetry meeting =
The telemetry project team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code>:
* '''every''' week on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].

[https://www.google.com/calendar/ical/h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com/public/basic.ics ICAL link for the meeting schedule]

[https://www.google.com/calendar/embed?src=h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com&ctz=UTC HTML view of schedule in UTC]

Everyone is welcome.

The blueprints that are used as a basis for the telemetry project can be found [https://blueprints.launchpad.net/ceilometer here]. We are currently sharing the ceilometer space until aodh and gnocchi requirements warrant segregated management. For now, to ensure collaboration, the space will remain shared.

The process of proposing a new blueprint from Juno onwards is described [https://wiki.openstack.org/wiki/Blueprints#Blueprints_and_Specs here].

=== Agenda ===

'''Please add your name with the agenda item, so we know who to call on during the meeting.'''
* recurring: roadmap items (new/old/blockers) https://wiki.openstack.org/wiki/Telemetry/RoadMap
* aodh topics
* ceilometer topics
* gnocchi topics
* Open discussion

=== Apologies for absence ===

== Previous meetings ==
* [http://eavesdrop.openstack.org/meetings/telemetry/2015 2015]

=== HIstorical Ceilometer meetings ===
* [http://eavesdrop.openstack.org/meetings/ceilometer/2015 2015]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2014 2014]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2013 2013]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2012 2012]

=== Historical pre-Ceilometer meetings ===
* meeting 16 | 16 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.html summary]
* meeting 15 | 09 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.html summary]
* meeting 14 | 02 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.html summary]
* meeting 13 | 26 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.html summary]
* meeting 12 | 19 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.html summary]
* meeting 11 | 12 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.log.html log]
* meeting 10 | 05 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.log.html log]
* meeting 9 | 28 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.log.html log]
* meeting 8 | 21 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.log.html log]
* meeting 7 | 13 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.log.html log]
* meeting 6 | 7 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.log.html log]
* meeting 5 | 31 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.log.html log]
* meeting 4 | 24 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.log.html log]
* meeting 3 | 17 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.log.html log]
* meeting 2 | 10 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html log]
* meeting 1 | 3 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.log.html log]
* meeting 0 | 26 apr 12 | [[Meetings/MeteringAgenda/meeting-0-summary|summary]] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.log.html log]

== Meeting organizers ==
* Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
* Use http://meetbot.debian.net/Manual.html to get an automatic summary
* Prepare an outline for the meeting to speed things up
<pre><nowiki>
#startmeeting telemetry
#topic some action from previous meeting
#topic something interesting
#topic Open discussion
#endmeeting
</nowiki></pre>

* Update == Agenda for next meeting ==
* Mail the automatic summary as a reply to the invitation

Meetings/Telemetry

2015-11-19T16:28:48Z

Gordon chung:

= Mid-Cycles =

The telemetry team will not hold a midcycle for Mitaka. A virtual one will be discussed for January if required.

Past Midcycles

* [[Meetings/Ceilometer/Liberty Virtual Mid-Cycle|Liberty Virtual Mid-Cycle]]

= Weekly Telemetry meeting =
The telemetry project team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code>:
* '''every''' week on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].

[https://www.google.com/calendar/ical/h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com/public/basic.ics ICAL link for the meeting schedule]

[https://www.google.com/calendar/embed?src=h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com&ctz=UTC HTML view of schedule in UTC]

Everyone is welcome.

The blueprints that are used as a basis for the telemetry project can be found [https://blueprints.launchpad.net/ceilometer here]. We are currently sharing the ceilometer space until aodh and gnocchi requirements warrant segregated management. For now, to ensure collaboration, the space will remain shared.

The process of proposing a new blueprint from Juno onwards is described [https://wiki.openstack.org/wiki/Blueprints#Blueprints_and_Specs here].

=== Agenda ===

'''Please add your name with the agenda item, so we know who to call on during the meeting.'''
* recurring: roadmap items (new/old/blockers) https://wiki.openstack.org/wiki/Telemetry/RoadMap
* aodh topics
* ceilometer topics
* gnocchi topics
* spec for new project with polling and notification (ityaptin)
* Open discussion

=== Apologies for absence ===

== Previous meetings ==
* [http://eavesdrop.openstack.org/meetings/telemetry/2015 2015]

=== HIstorical Ceilometer meetings ===
* [http://eavesdrop.openstack.org/meetings/ceilometer/2015 2015]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2014 2014]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2013 2013]
* [http://eavesdrop.openstack.org/meetings/ceilometer/2012 2012]

=== Historical pre-Ceilometer meetings ===
* meeting 16 | 16 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.html summary]
* meeting 15 | 09 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.html summary]
* meeting 14 | 02 aug 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-16.00.html summary]
* meeting 13 | 26 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-26-16.01.html summary]
* meeting 12 | 19 jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-19-16.03.html summary]
* meeting 11 | 12 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-12-16.00.log.html log]
* meeting 10 | 05 Jul 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-05-16.00.log.html log]
* meeting 9 | 28 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-28-16.01.log.html log]
* meeting 8 | 21 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-21-16.00.log.html log]
* meeting 7 | 13 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-14-16.00.log.html log]
* meeting 6 | 7 jun 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-07-16.01.log.html log]
* meeting 5 | 31 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-31-16.02.log.html log]
* meeting 4 | 24 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-24-16.01.log.html log]
* meeting 3 | 17 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-17-16.01.log.html log]
* meeting 2 | 10 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html log]
* meeting 1 | 3 may 12 | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.log.html log]
* meeting 0 | 26 apr 12 | [[Meetings/MeteringAgenda/meeting-0-summary|summary]] | [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-26-16.00.log.html log]

== Meeting organizers ==
* Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
* Use http://meetbot.debian.net/Manual.html to get an automatic summary
* Prepare an outline for the meeting to speed things up
<pre><nowiki>
#startmeeting telemetry
#topic some action from previous meeting
#topic something interesting
#topic Open discussion
#endmeeting
</nowiki></pre>

* Update == Agenda for next meeting ==
* Mail the automatic summary as a reply to the invitation