Difference between revisions of "Meetings/TechnicalCommittee/Ceilometer Gap Coverage"
(→Concern #3: lack of coverage in integration tests) |
(→Concern #2: lack of user- and operator-oriented documentation) |
||
| Line 9: | Line 9: | ||
=== Concern #2: lack of user- and operator-oriented documentation === | === Concern #2: lack of user- and operator-oriented documentation === | ||
* Actions: | * Actions: | ||
| − | + | # joint ceilometer/documentation [http://summit.openstack.org/cfp/details/311 summit design session] | |
| − | + | # address persistent issues in the ceilometer documentation build | |
| − | + | # move non-developer-oriented installation instructions out of the in-tree developer documentation | |
| + | # re-work [http://openstack.redhat.com/CeilometerQuickStart RDO getting started guide] in [https://blueprints.launchpad.net/openstack-manuals/+spec/add-ceilometer-admin-guide-to-openstack-manuals distro-agnostic form] | ||
* Driver: ildikov | * Driver: ildikov | ||
* Milestone targets: | * Milestone targets: | ||
** Initial progress by: juno-1 | ** Initial progress by: juno-1 | ||
** Completed by: juno-2 | ** Completed by: juno-2 | ||
| − | * Status: '''in progress''' | + | * Status: '''#1-2 completed, #3-4 in progress''' |
=== Concern #3: lack of coverage in integration tests === | === Concern #3: lack of coverage in integration tests === | ||
Revision as of 12:19, 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:
- 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
- move non-developer-oriented installation instructions out of the in-tree developer documentation
- re-work RDO getting started guide in distro-agnostic form
- Driver: ildikov
- Milestone targets:
- Initial progress by: juno-1
- Completed by: juno-2
- Status: #1-2 completed, #3-4 in progress
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
- Drivers: DinaBelova/vrovachev
- Milestone targets:
- Substantial progress by: juno-1
- Completed by: juno-2
- Status: #1-3 completed, #4 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:
- Substantial progress by by: juno-1
- Completed by: juno-2
- Status: #1 completed, #2 in-progress
