<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 12/27/2013 05:27 AM, Nadya Privalova
wrote:<br>
</div>
<blockquote
cite="mid:CAKWrcJdSnTTwwJ3YghfdHonvUN_G_3LWHzGemQGjEqJ35s=W8g@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Hello guys!<br>
<br>
</div>
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 :) <br>
</div>
After the summit we decided to track all tests
that are being created for Ceilometer in
Tempest here: <a moz-do-not-send="true"
href="https://blueprints.launchpad.net/tempest/+spec/add-basic-ceilometer-tests">https://blueprints.launchpad.net/tempest/+spec/add-basic-ceilometer-tests</a>.
Besides, we've created an etherpad page with a
test plan <a moz-do-not-send="true"
href="https://etherpad.openstack.org/p/ceilometer-test-plan">https://etherpad.openstack.org/p/ceilometer-test-plan</a>.<br>
<br>
</div>
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 <span id="result_box" class="" lang="en"><span
class="">reliable mechanism for tracking any
changes.</span></span> </div>
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.<br>
</div>
So there are the following action items:<br>
</div>
1. Resolve all conflicts in changes that are on review
now (see my comment to <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/39237/">https://review.openstack.org/#/c/39237/</a>
patch set 21 for more details)<br>
</div>
2. Create set of blueprints from the testplan we have<br>
</div>
3. Add Tempest discussions to Ceilometer weekly meeting
agenda (done)<br>
<br>
</div>
I may take care of all the items above. I need only "ok"
from PTLs and Cores. <br>
</div>
Anyway, we've started working on 1st item, because it is
urgent. The second one may be postponed due to holidays. <br>
<br>
</div>
And one more important thing. Code review for Ceilometer tests
in Tempest is too slow. Some of change requests are created
almost a half a year ago! Ceilometer guys, please be informed. I
think all of us are interested in good tests.<br>
<div>
<div>
<div>
<div>
<div><br>
</div>
<div>Thank you for attention,<br>
</div>
<div>Nadya<br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
Thanks, Nadya. A similar issue came up with heat. The problem is
that tempest really has two parts: the tempest infrastructure
itself, and all the test files for the various projects. The tempest
team needs to manage its blueprints and we can't do that if there
are dozens of blueprints about test implementation across projects.
This problem is exacerbated by the fact that launchpad is not a good
tool for project management which is the issue you are dealing with.
For now, the best thing would be to have a master blueprint in
tempest. If you want it to point to sub-blueprints for various test
areas, use blueprints in the ceilometer project rather than tempest.<br>
<br>
-David<br>
<br>
<blockquote
cite="mid:CAKWrcJdSnTTwwJ3YghfdHonvUN_G_3LWHzGemQGjEqJ35s=W8g@mail.gmail.com"
type="cite">
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>