Jump to: navigation, search

Difference between revisions of "Telemetry/RoadMap"

(Ceilometer (data collection))
(Road Map)
Line 1: Line 1:
 
= Road Map =
 
= Road Map =
  
Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka
+
'''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
 
* items from summit - https://etherpad.openstack.org/p/mitaka-telemetry-todos
Line 22: Line 24:
 
* use oslo.messaging batch notification listener
 
* use oslo.messaging batch notification listener
 
* adopt oslo.db pagination
 
* adopt oslo.db pagination
* mongo/hbase to sql backend convertor tool
 
* fix services to use python-aodhclient rather than python-ceilometerclient.
 
  
 
=== Ceilometer (data collection) ===
 
=== Ceilometer (data collection) ===
* add elasticsearch functional gate
 
 
* Polling schema - separate polling logic from pipeline
 
* Polling schema - separate polling logic from pipeline
 
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
 
** new polling definition file https://etherpad.openstack.org/p/mitaka-telemetry-polling
 +
* multiple meter/event definition file support
 
* refine polling
 
* refine polling
** global caching between pollsters (https://etherpad.openstack.org/p/mitaka-telemetry-polling)
+
** drop metadata polling requirements
* Cache everything everywhere, all the time
+
* deprecate ceilometer-api
** add to sql driver
 
 
* generic notification agent
 
* generic notification agent
 
* rally tests
 
* rally tests
Line 39: Line 38:
 
* indexer sharding support
 
* indexer sharding support
 
* benchmark rewrite, generating load with python is not efficient enough for good benchmarking
 
* 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
 
* migrate tempest plugin
  
Line 46: Line 47:
 
* log processing
 
* log processing
 
* application level monitoring
 
* 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.
 
* 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 cell metrics
 
** nova availability zone metrics
 
** nova availability zone metrics
Line 55: Line 53:
 
* granular ttl control (project level / meter level)
 
* granular ttl control (project level / meter level)
 
* CADF event indexer - generic definition to index all CADF events
 
* CADF event indexer - generic definition to index all CADF events
* stop using WSME in ceilometer and aodh
+
* stop using WSME in aodh
* Release to PyPI
 
 
* Use specific configuration to load selected stevedore extensions, not all of them
 
* Use specific configuration to load selected stevedore extensions, not all of them
 
** remove stevedore plugins out of tree
 
** remove stevedore plugins out of tree
Line 63: Line 60:
  
 
== Past Cycles ==
 
== Past Cycles ==
 +
* Newton: https://blueprints.launchpad.net/ceilometer/newton
 +
* Mitaka: https://blueprints.launchpad.net/ceilometer/mitaka
 
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
 
* Liberty: https://blueprints.launchpad.net/ceilometer/liberty
 
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
 
* Kilo: https://blueprints.launchpad.net/ceilometer/kilo
 
* Juno: https://blueprints.launchpad.net/ceilometer/juno
 
* Juno: https://blueprints.launchpad.net/ceilometer/juno

Revision as of 13:21, 2 November 2016

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

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:

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
  • 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
  • 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