Jump to: navigation, search

Difference between revisions of "Ceilometer"

m (Future Targets)
(OpenStack Telemetry (Ceilometer))
Line 32: Line 32:
 
== Road Map ==
 
== Road Map ==
  
Current (Liberty) Cycle Targets: https://blueprints.launchpad.net/ceilometer/liberty
+
The future direction and plans of the project can be found [[Ceilometer/RoadMap|here]].
 
 
=== Priority Work Items ===
 
The following are high priority items targeted for the current cycle that require owners:
 
 
 
* document operator changes from alarm in Ceilometer to alarm in Aodh
 
** to be followed by email to operators list
 
 
 
=== 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-ceilometer. The current list of core contributors are: https://launchpad.net/~ceilometer-drivers/+members#active
 
 
 
* [https://bugs.launchpad.net/ceilometer/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&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&search=Search triaged or confirmed bugs]
 
* Gnocchi
 
** gate
 
** client
 
** indexer sharding support
 
** dispatcher optimisation (batching)
 
** revisit gnocchi resource definition
 
** benchmark
 
* Alarms (Aodh)
 
** Devstack gate
 
** some plugin stuff mehdi is suppose to do
 
* in-tree functional tests
 
** split unit/functional tests
 
** add mysql/postgres functional gate
 
** add elasticsearch functional gate
 
** performance rally tests
 
* Code Refactoring
 
** Split - split polling (M* cycle) https://etherpad.openstack.org/p/ceilometer-collection-split
 
** Removal - remove deprecated alarm code (M* cycle) https://etherpad.openstack.org/p/aodh-future
 
 
 
=== 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
 
 
 
=== Past Cycles ===
 
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
 
* Juno: https://blueprints.launchpad.net/ceilometer/juno
 
  
 
== Contributing to Ceilometer ==
 
== Contributing to Ceilometer ==

Revision as of 22:04, 12 July 2015

OpenStack Telemetry (Ceilometer)

Source code https://github.com/openstack/ceilometer
Bug tracker https://bugs.launchpad.net/ceilometer
Specs https://github.com/openstack/ceilometer-specs
Blueprints https://blueprints.launchpad.net/ceilometer
Developer doc http://docs.openstack.org/developer/ceilometer/
FAQ https://ask.openstack.org/questions/scope:all/sort:activity-desc/tags:ceilometer/
Tarballs http://tarballs.openstack.org/ceilometer/
Meetings https://wiki.openstack.org/wiki/Meetings/Ceilometer

Project Mission

To reliably collect measurements of 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.

Road Map

The future direction and plans of the project can be found here.

Contributing to Ceilometer

The developer documentation is starting to take shape within the source and is also published at http://docs.openstack.org/developer/ceilometer/.

The project team hangs out on Freenode in the #openstack-ceilometer 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 Ceilometer please tag the message subject with [Ceilometer].

The project team officially meets once a week, see Meetings/Ceilometer.

More details can be found on possible contributions at Ceilometer/Contributing including:

  • Setting-up Ceilometer via devstack
  • Possible tasks
    • Update documentation
    • Close old fixed bugs
    • Fix bugs
    • Review patches
    • Triage incoming bugs
  • and more...