<div dir="ltr">Hello all,<div><br></div><div>Thank you for your suggestions about tracking bps. I'll create a spreadsheet.</div><div><br></div><div>David,</div><div><br></div><div>1. <a href="https://review.openstack.org/#/c/55276/">https://review.openstack.org/#/c/55276/</a> is ready for review</div>
<div><div class="gmail_extra" style>2. We decided to move base.py to a separate change request: <a href="https://review.openstack.org/#/c/64304/">https://review.openstack.org/#/c/64304/</a> to make it merged ASAP. But now I see that reviewers want to see an example of usage. We didn't wanted to add any examples there. There are several changes that are abandoned now but will be restored soon with dependency on 64304 (<a href="https://review.openstack.org/#/c/43481/">https://review.openstack.org/#/c/43481/</a>, <a href="https://review.openstack.org/#/c/46745/">https://review.openstack.org/#/c/46745/</a>). What do you think is it OK to keep 64304 as a separate one? </div>
<div class="gmail_extra" style>3. <a href="https://review.openstack.org/#/c/39237/">https://review.openstack.org/#/c/39237/</a> is In Progress because it should be depended on 2. <br></div><div class="gmail_extra" style>4. Not sure why <a href="https://review.openstack.org/#/c/64299/">https://review.openstack.org/#/c/64299/</a> is a separate one. It is a part of 1 now. I think it should be abandoned.</div>
<div class="gmail_extra" style><br></div><div class="gmail_extra" style>And about <span style="font-family:arial,sans-serif;font-size:13px">"ceilometer", "metering", "telemetry". Originally 'metering' was used, but official was changed to 'telemetry'. I'm not the person who resolved such questions but I guess that 'telemetry' is the final solution. Anyway, I will discuss it with Julien.</span></div>
<div class="gmail_extra" style><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div class="gmail_extra" style><span style="font-family:arial,sans-serif;font-size:13px">Thanks,</span></div><div class="gmail_extra" style>
<span style="font-family:arial,sans-serif;font-size:13px">Nadya</span></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 30, 2013 at 11:53 PM, David Kranz <span dir="ltr"><<a href="mailto:dkranz@redhat.com" target="_blank">dkranz@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div class="im">
<div>On 12/27/2013 05:27 AM, Nadya Privalova
wrote:<br>
</div>
</div><div><div class="h5"><blockquote 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 href="https://blueprints.launchpad.net/tempest/+spec/add-basic-ceilometer-tests" target="_blank">https://blueprints.launchpad.net/tempest/+spec/add-basic-ceilometer-tests</a>.
Besides, we've created an etherpad page with a
test plan <a href="https://etherpad.openstack.org/p/ceilometer-test-plan" target="_blank">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 lang="en"><span>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 href="https://review.openstack.org/#/c/39237/" target="_blank">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>
<br>
<fieldset></fieldset>
<br>
</blockquote></div></div>
So the tempest patches for ceilometer are still not a coherent set.
Can you please mark anything that is not ready for review as Work In
Progress, or abandon until there is really something to review?<br>
<br>
Also, having looked at a few of these, I am confused about the usage
of "ceilometer", "metering", "telemetry". Is there an explanation
for the context in which each of these terms is to be used?<span class=""><font color="#888888"><br>
<br>
-David<br>
<br>
<br>
</font></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div></div>