Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee/Ceilometer Gap Coverage"

(Concern #1: lack of an explicit project mission statement)
(Concern #3: lack of coverage in integration tests)
Line 20: Line 20:
 
=== Concern #3: lack of coverage in integration tests ===
 
=== Concern #3: lack of coverage in integration tests ===
 
* Actions:
 
* Actions:
** detailed analysis of current coverage https://etherpad.openstack.org/p/ceilometer-tempest-status
+
# [http://summit.openstack.org/cfp/details/152 summit design session] to address test strategy shortcomings  
** TL;DR: need to solve "performant only with the storage driver we don't gate on" conumdrum
+
# [https://review.openstack.org/96752 leverage] the ceilometer capabilities API to make the viable sql-a driver discoverable in branchless Tempest 
** summit design session to address test strategy shortcomings http://summit.openstack.org/cfp/details/152
+
# land the [https://review.openstack.org/#/q/status:merged+project:openstack/tempest+branch:master+topic:bp/add-basic-ceilometer-tests,n,z stalled tempest patches]
 +
# curate the ceilometer Tempest coverage to ensure it does not become persistently problematic in the gate
 
* Drivers: DinaBelova/vrovachev
 
* Drivers: DinaBelova/vrovachev
 
* 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 #4: lack of production-readiness of sqlalchemy driver ===
 
=== Concern #4: lack of production-readiness of sqlalchemy driver ===

Revision as of 12:13, 14 June 2014

Concern #1: lack of an explicit project mission statement

  • Actions:
  • Driver: eglynn
  • Milestone targets:
    • Completed by: juno-1
  • Status: completed

Concern #2: lack of user- and operator-oriented documentation

Concern #3: lack of coverage in integration tests

  • Actions:
  1. summit design session to address test strategy shortcomings
  2. leverage the ceilometer capabilities API to make the viable sql-a driver discoverable in branchless Tempest
  3. land the stalled tempest patches
  4. 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:
  1. summit design session to address inefficiencies inherent in the current data model
  2. initial round of improvements required for sqlalchemy driver to be viable in the gate / small PoCs
  3. leverage sqlalchemy author Mike Bayer's domain expertise
  4. 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:
  1. ceilometer services included in the existing grenade sequencing
  2. 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