Difference between revisions of "Telemetry"
Gordon chung (talk | contribs) m |
Gordon chung (talk | contribs) m (→Managed) |
||
| (11 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
= OpenStack Telemetry = | = OpenStack Telemetry = | ||
| − | |||
| − | |||
== Project Mission == | == 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. | 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/aodh Aodh] - an alarming service | ||
* [https://github.com/openstack/ceilometer Ceilometer] - a data collection service | * [https://github.com/openstack/ceilometer Ceilometer] - a data collection service | ||
| − | * [https://github.com/ | + | * [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" | {| border="1" cellpadding="2" cellspacing="0" | ||
| Source code | | Source code | ||
| − | | https://github.com/openstack/ | + | | https://github.com/openstack/aodh |
| + | |- | ||
| + | | Blueprints | ||
| + | | https://blueprints.launchpad.net/aodh | ||
|- | |- | ||
| Bug tracker | | Bug tracker | ||
| − | | https://bugs.launchpad.net/ | + | | https://bugs.launchpad.net/aodh |
| + | |- | ||
| + | | Developer doc | ||
| + | | http://docs.openstack.org/developer/aodh/ | ||
|- | |- | ||
| − | | | + | | Tarballs |
| − | | https://github.com/openstack/ceilometer | + | | 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 | | Blueprints | ||
| https://blueprints.launchpad.net/ceilometer | | https://blueprints.launchpad.net/ceilometer | ||
|- | |- | ||
| − | | | + | | Bug tracker |
| − | | | + | | https://bugs.launchpad.net/ceilometer |
|- | |- | ||
| Developer doc | | Developer doc | ||
| http://docs.openstack.org/developer/ceilometer/ | | http://docs.openstack.org/developer/ceilometer/ | ||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| Tarballs | | Tarballs | ||
| http://tarballs.openstack.org/ceilometer/ | | 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 === | === Externally Managed === | ||
| − | * [https://github.com/openstack/heat Heat] - Orchestration service which provides autoscaling capabilities using Ceilometer data | + | * [https://github.com/openstack/heat Heat] - Orchestration service which provides autoscaling capabilities using Ceilometer data. |
| − | * [https://github.com/openstack/horizon Horizon] - UI service which | + | * [https://github.com/openstack/horizon Horizon] - UI service which allows interaction with Aodh data. |
| − | * [https://github.com/stackforge/ceilometer-powervm PowerVM] - PowerVM pollster plugin | + | * [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/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/spilgames/ceilometer_graphite_publisher Graphite Publisher] - Ceilometer publisher to connect to Graphite. | ||
| − | * [https://github.com/openstack/watcher Watcher] - Resource optimization service | + | * [https://github.com/openstack/watcher Watcher] - Resource optimization service. |
| − | * [http://icclab.github.io/cyclops Cyclops] - Rating-Charging-Billing Solution for Cloud providers | + | * [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. | ||
| − | |||
| − | |||
| − | The | + | == 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 project team | + | 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: | + | [[Category:Telemetry]] |
Revision as of 16:43, 29 May 2017
Contents
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:
- Aodh - an alarming service
- Ceilometer - a data collection service
- Gnocchi - a time-series database and resource indexing service
- Panko - an event, metadata indexing service
| 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
| 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.
| 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.
| 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)
| 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
- Heat - Orchestration service which provides autoscaling capabilities using Ceilometer data.
- Horizon - UI service which allows interaction with Aodh data.
- PowerVM - PowerVM pollster plugin. Owners: thorst and efried. IRC: #openstack-powervm
- CloudKitty - OpenStack Rating as a Service component and usage reporting.
- Graphite Publisher - Ceilometer publisher to connect to Graphite.
- Watcher - Resource optimization service.
- Cyclops - Rating-Charging-Billing Solution for Cloud providers.
- Collectd - A Collectd writer plugin to publish telemetry to Gnocchi.
Road Map
The future direction and plans of the project can be found 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 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.
