Difference between revisions of "Meetings/TechnicalCommittee/Ceilometer Gap Coverage"
(→Concern #5: lack of participation in Grenade-based upgrade testing) |
(→Concern #4: lack of production-readiness of sqlalchemy driver) |
||
| Line 31: | Line 31: | ||
=== Concern #4: lack of production-readiness of sqlalchemy driver === | === Concern #4: lack of production-readiness of sqlalchemy driver === | ||
* Actions: | * Actions: | ||
| − | + | # [http://summit.openstack.org/cfp/details/163 summit design session] to address inefficiencies inherent in the current data model | |
| − | + | # initial [https://blueprints.launchpad.net/ceilometer/+spec/big-data-sql round of improvements] required for sqlalchemy driver to be viable in the gate / small PoCs | |
| − | + | # [https://etherpad.openstack.org/p/ceilometer-sqlalchemy-mike-bayer leverage] sqlalchemy author Mike Bayer's domain expertise | |
| − | + | # allow Juno-derived distros treat sqlalchemy as a first-class citizen in small production deployments | |
| − | |||
| − | |||
* Driver: gordc | * Driver: gordc | ||
* Milestone targets: | * Milestone targets: | ||
** Substantial progress by: juno-1 | ** Substantial progress by: juno-1 | ||
** Completed by: juno-2 | ** Completed by: juno-2 | ||
| − | * Status: '''in progress''' | + | * Status: '''#1-3 completed, #4 in progress''' |
=== Concern #5: lack of participation in Grenade-based upgrade testing === | === Concern #5: lack of participation in Grenade-based upgrade testing === | ||
Revision as of 10:02, 14 June 2014
Contents
- 1 Concern #1: lack of an explicit project mission statement
- 2 Concern #2: lack of user- and operator-oriented documentation
- 3 Concern #3: lack of coverage in integration tests
- 4 Concern #4: lack of production-readiness of sqlalchemy driver
- 5 Concern #5: lack of participation in Grenade-based upgrade testing
Concern #1: lack of an explicit project mission statement
- Actions:
- team wordsmithing of an appropriate mission statement: https://review.openstack.org/87526
- Driver: eglynn
- Milestone targets:
- Completed by: juno-1
- Status: completed
Concern #2: lack of user- and operator-oriented documentation
- Actions:
- re-work RDO getting started guide in distro-agnostic form: http://openstack.redhat.com/CeilometerQuickStart
- discern operator preferences for documentation at summit operator feedback session: http://summit.openstack.org/cfp/details/177
- joint ceilometer/documentation summit session: http://summit.openstack.org/cfp/details/311
- Driver: ildikov
- Milestone targets:
- Initial progress by: juno-1
- Completed by: juno-2
- Status: in progress
Concern #3: lack of coverage in integration tests
- Actions:
- detailed analysis of current coverage https://etherpad.openstack.org/p/ceilometer-tempest-status
- TL;DR: need to solve "performant only with the storage driver we don't gate on" conumdrum
- summit design session to address test strategy shortcomings http://summit.openstack.org/cfp/details/152
- Drivers: DinaBelova/vrovachev
- Milestone targets:
- Substantial progress by: juno-1
- Completed by: juno-2
- Status: in progress
Concern #4: lack of production-readiness of sqlalchemy driver
- Actions:
- summit design session to address inefficiencies inherent in the current data model
- initial round of improvements required for sqlalchemy driver to be viable in the gate / small PoCs
- leverage sqlalchemy author Mike Bayer's domain expertise
- allow Juno-derived distros treat sqlalchemy as a first-class citizen in small production deployments
- Driver: gordc
- Milestone targets:
- Substantial progress by: juno-1
- Completed by: juno-2
- Status: #1-3 completed, #4 in progress
Concern #5: lack of participation in Grenade-based upgrade testing
- Actions:
- ceilometer services included in the existing grenade sequencing
- ceilometer-specific assertions on resource survivability in "javelin2"
- Drivers: emilienm/cdent
- Milestone targets:
- Phase1 to be completed by: juno-1
- Phase2 to be completed by: juno-2
- Status: phase1 completed, phase2 in-progress
