Jump to: navigation, search

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

(Concern #4: lack of production-readiness of sqlalchemy driver)
(Concern #5: lack of participation in Grenade-based upgrade testing)
Line 47: Line 47:
 
* Drivers: emilienm/cdent
 
* Drivers: emilienm/cdent
 
* Milestone targets:
 
* Milestone targets:
** Phase1 to be completed by: juno-1
+
** Substantial progress by by: juno-1
** Phase2 to be completed by: juno-2
+
** Completed by: juno-2
* Status: '''phase1 completed, phase2 in-progress'''
+
* Status: '''#1 completed, #2 in-progress'''

Revision as of 10:03, 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

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