Meetings/TechnicalCommittee/Trove Gap Coverage
Contents
Concern #1: Lack of Test Coverage in Tempest
- Actions:
- BP for Juno is at https://blueprints.launchpad.net/tempest/+spec/tempest-guest-tests and is a top priority
- We have already started working on adding more tests: https://etherpad.openstack.org/p/trove-tempest-items
- This was one of the main points discussed at the Icehouse Trove Midcycle meetup: https://etherpad.openstack.org/p/trove-2014-meetup-tempest
- Planning to iron out any issues that may arise during the Trove Testing Session at the ATL Design Summit: http://summit.openstack.org/cfp/details/295
- On a slightly tangential note, we are going to start looking into upgrade testing / grenade as well.
- Driver(s): peterstac, ravikumar_hp, vipuls
- Milestone: Juno 3
slicknik (talk) 16:57, 6 October 2014 (UTC)We have made good progress towards adding new tests to Tempest to increase API coverage - we are continuing to do so, and will keep doing so during kilo. We have not started to look into grenade testing, but are planning to do so in kilo. slicknik (talk) 17:04, 5 December 2014 (UTC) This is now completed as of the beginning of kilo-1
Concern #2: Trove Documentation
- Actions:
- We now have an Trove deployment doc published at http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_trove.html
- However, this is a draft and has gaps which need to be filled in (esp. around building guestagent images).
- Getting the quality up on this is a high priority for Juno
- We have trove-api docs at https://github.com/openstack/database-api
- Currently in the process of moving them over to the trove repository for better locality so it makes it easier to update
- Update build jobs to build automatically
- Update with datastore API details
- We also have trove developer docs at http://docs.openstack.org/developer/trove/ which get built automatically by an infra job
- Will update and polish this in Juno
- We now have an Trove deployment doc published at http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_trove.html
- Driver(s): grapex, laurelm
- Milestone:Juno 3
slicknik (talk) 17:05, 6 October 2014 (UTC) API docs are now moved over to the trove repo (https://review.openstack.org/#/c/87807/). We are in the process of polishing up the docs including the deployment doc. Details on that effort, as well as patch-sets up for review can be found at https://etherpad.openstack.org/p/trove-doc-items
Concern #3: Deprecating Reddwarf CI
- Actions:
- Identify "functional tests" in trove-integration that are not "integration tests" and not movable to Tempest, but still needed.
- Move these functional tests that are running as part of rdjenkins test job today to run as a new Openstack Infra job.
- Retire rdjenkins functional test-job, and currently used gerrit trigger plugin workflow.
- Driver(s): juice, slicknik
- Milestone: Juno 3
slicknik (talk) 17:06, 6 October 2014 (UTC) This is still WIP. The patches for the infra experimental job for this is done (https://review.openstack.org/#/c/105692/), but we're still running into a couple of config issues with running the tests in a d-g environment that we are working through. We hope to have this wrapped up during kilo-1.
Concern #4: BPs, Bug Triage, and Reviews
- Actions:
- We now have a weekly bp review meeting in #openstack-trove to triage/approve BPs
- We've historically had issues with BPs not having sufficient info in them, so we now have a template that BPs must follow before they can be approved. https://wiki.openstack.org/wiki/TroveBlueprint
- Dedicated some time to do focused bug triage.
- Need to expand core team to get better traction with reviews. Discussions around this to happen at the ATL design summit.
- Driver(s): slicknik, hub_cap, amcrn
- Milestone: Juno 1 (done)
Concern #5: Neutron Support
- Actions:
- Support deployments using Neutron
- This includes automated testing in openstack-infra of this configuration (overlap with gap #3)
- Driver(s): annashen, juice, slicknik
- Milestone: Juno 2 (done)
slicknik (talk) 17:08, 29 July 2014 (UTC) This is completed: https://review.openstack.org/#/c/78123/ and https://review.openstack.org/#/c/88349/