Add Initial Trove Integration Tests to Tempest

Registered by Nikhil Manchanda on 2013-10-24

The goal of this blueprint is to have Trove Integration tests running as part of Tempest.

In order to achieve this, a number of smaller work items need to happen:

1. Trove dib elements need to be moved out into a separate repo, so that a dib run can build the guestagent.

2. Make job on devstack gate on this repo to build dib guestagent Ubuntu and Fedora images on repo changes.

3. Once built, the job publishes the images to a location (tarballs.o.o?) for caching.

4. Update tempest to write integration tests for Trove that can run on devstack-gate. These tests can use the cached image.

More details and notes from the summit session can be found here :
https://etherpad.openstack.org/p/TroveTempestTesting

Blueprint information

Status:
Complete
Approver:
None
Priority:
High
Drafter:
Nikhil Manchanda
Direction:
Needs approval
Assignee:
Nikhil Manchanda
Definition:
Approved
Series goal:
Accepted for icehouse
Implementation:
Implemented
Milestone target:
milestone icon 2014.1
Started by
Nikhil Manchanda on 2013-12-03
Completed by
Nikhil Manchanda on 2014-03-10

Related branches

Sprints

Whiteboard

Notes:
IceHouse Summit Notes and Work Items: https://etherpad.openstack.org/p/TroveTempestTesting
High level list of Trove Tests to Port: https://etherpad.openstack.org/p/trove-tempest-items

Reviews:
(MERGED) Handle trove service availabilty in tempest: https://review.openstack.org/#/c/64913/
(MERGED) Update devstack-gate jobs for Trove tempest tests: https://review.openstack.org/#/c/65065/
(MERGED) Add Trove testing support: https://review.openstack.org/#/c/65040/
(MERGED) Add Trove (database) Flavor API Tests: https://review.openstack.org/#/c/69501/

(?)

Work Items

Work items:
[debasish-chowdhury] Create python-troveclient tests : TODO
[slicknik] Create Trove API tests : DONE
[slicknik] Overhaul devstack to include trove out of the box : DONE
[slicknik] Include tempest configuration to enable trove : DONE

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.