Jump to: navigation, search

Meetings/TechnicalCommittee/Ceilometer Gap Coverage

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

  • Actions:
  1. joint ceilometer/documentation summit design session
  2. address persistent issues in the ceilometer documentation build
  3. re-work RDO getting started guide in distro-agnostic form
  4. 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-2 juno-3
  • Status: #1-2 completed, #3-4 completed

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
  5. 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-2 juno-3
  • Status: #1-3 completed, #4 in progress, #5 completed

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 juno-3
  • Status: #1-3 completed, #4 completed

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 juno-3
  • Status: #1 completed, #2 completed