[openstack-dev] [Ceilometer][Tempest]Tracking of blueprints and changes

Christopher Yeoh cbkyeoh at gmail.com
Fri Dec 27 23:36:59 UTC 2013


On Fri, Dec 27, 2013 at 8:57 PM, Nadya Privalova <nprivalova at mirantis.com>wrote:

> Hello guys!
>
> I hope all of you are enjoying the holidays! But I'd like to raise a
> Tempest question. Again. I hope this email will not be lost after vacations
> :)
> After the summit we decided to track all tests that are being created for
> Ceilometer in Tempest here:
> https://blueprints.launchpad.net/tempest/+spec/add-basic-ceilometer-tests.
> Besides, we've created an etherpad page with a test plan
> https://etherpad.openstack.org/p/ceilometer-test-plan.
>
> But it turned out that it works very bad. Now we have at least 3 change
> requests that have common functionality implemented. So we definitely need
> more reliable mechanism for tracking any changes.
> That's why I suggest to create a separate blueprint for each
> functionality. E.g. "Ceilometer client for Tempest", "Notification testing"
> with several bps that depend on it ("Swift notifications", "Glance
> notifications", "Nova notifications") and so on. In future we may vary the
> detail level of blueprints but now we need very detailed ones because
> different people have started to work on e.g. notifications.
> So there are the following action items:
> 1. Resolve all conflicts in changes that are on review now (see my comment
> to https://review.openstack.org/#/c/39237/ patch set 21 for more details)
> 2. Create set of blueprints from the testplan we have
> 3. Add Tempest discussions to Ceilometer weekly meeting agenda (done)
>
>
So you might want to consider setting up something like this:

https://docs.google.com/spreadsheet/ccc?key=0AmYuZ6T4IJETdEVNTWlYVUVOWURmOERSZ0VGc1BBQWc&usp=drive_web#gid=0

which was done for the Nova API testing where we have lots of people
working on tests simultaneously but don't want people accidentally
duplicating effort.

Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131228/9c294fd8/attachment.html>


More information about the OpenStack-dev mailing list