Difference between revisions of "Meetings/TechnicalCommittee/Ceilometer Gap Coverage"
(→Concern #4: lack of production-readiness of sqlalchemy driver) |
m (ThierryCarrez moved page Governance/TechnicalCommittee/Ceilometer Gap Coverage to Meetings/TechnicalCommittee/Ceilometer Gap Coverage: TC pages moved to governance.o.o) |
(No difference)
|
Latest revision as of 16:34, 5 December 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:
- collaborative wordsmithing of an appropriate mission statement
- Driver: eglynn
- Milestone targets:
- Completed by: juno-1
- Status: completed
Concern #2: lack of user- and operator-oriented documentation
- Actions:
- joint ceilometer/documentation summit design session
- address persistent issues in the ceilometer documentation build
- re-work RDO getting started guide in distro-agnostic form
- move non-developer-oriented installation instructions out of the in-tree developer documentation
- Driver: ildikov
- Milestone targets:
- Initial progress by: juno-1
- Completed by:
juno-2juno-3
- Status: #1-2 completed, #3-4 completed
Concern #3: lack of coverage in integration tests
- Actions:
- summit design session to address test strategy shortcomings
- leverage the ceilometer capabilities API to make the viable sql-a driver discoverable in branchless Tempest
- land the stalled Tempest patches
- curate the ceilometer Tempest coverage to ensure it does not become persistently problematic in the gate
- further extend the ceilometer coverage in Tempest, including a mongodb-based Tempest variant once the distro coverage in the gate allows
- Drivers: DinaBelova/vrovachev
- Milestone targets:
- Substantial progress by: juno-1
- Completed by:
juno-2juno-3
- Status: #1-3 completed, #4 in progress, #5 completed
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-2juno-3
- Status: #1-3 completed, #4 completed
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