Difference between revisions of "Ceilometer/RoadMap"
Gordon chung (talk | contribs) m (→Road Map) |
Gordon chung (talk | contribs) m (→Road Map) |
||
| Line 1: | Line 1: | ||
== Road Map == | == Road Map == | ||
| − | Current ( | + | Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka |
=== Priority Work Items === | === Priority Work Items === | ||
| Line 53: | Line 53: | ||
=== Past Cycles === | === Past Cycles === | ||
| + | * 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 19:30, 9 November 2015
Road Map
Current (Mitaka) Cycle Targets: https://blueprints.launchpad.net/ceilometer/mitaka
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-ceilometer. The current list of core contributors are: https://launchpad.net/~ceilometer-drivers/+members#active
- triaged or confirmed bugs
- Gnocchi
- gate
- client
- indexer sharding support
- dispatcher optimisation (batching) (in reviews https://review.openstack.org/#/c/202589/ and https://review.openstack.org/#/c/202507/)
- revisit gnocchi resource definition (dispatcher side: https://review.openstack.org/#/c/202500/)
- benchmark
- Alarms (Aodh)
- Devstack gate
- in-tree functional tests
- 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
- Polling schema - separate polling logic from pipeline
- Rolling upgrades - queue based schema routing
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
- 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 POC)
- Add more complete evaluation of the upgrade process in the grenade plugin.
- Notification and pollster driven functional/integration tests.
