<div dir="ltr"><div class="gmail_default" style="font-size:small">The ceilometer collector is meant to scale horizontally. Have you tried configuring the test environment to run more than one copy, to process the notifications more quickly?</div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Doug</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 18, 2014 at 8:09 AM, Nadya Privalova <span dir="ltr"><<a href="mailto:nprivalova@mirantis.com" target="_blank">nprivalova@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div>Hi folks,<br><br></div>I'd like to discuss Ceilometer's tempest situation with you. <br>
</div>Now we have several patch sets on review that test core functionality of Ceilometer: notificaton and pollstering (topic <a href="https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/add-basic-ceilometer-tests,n,z" target="_blank">https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/add-basic-ceilometer-tests,n,z</a>). But there is a problem: Ceilometer performance is very poor on mysql and postgresql because of the bug <a href="https://bugs.launchpad.net/ceilometer/+bug/1291054" target="_blank">https://bugs.launchpad.net/ceilometer/+bug/1291054</a>. Mongo behaves much better even in single thread and I hope that it's performance will be enough to successfully run Ceilometer tempest tests. <br>
</div>Let me explain in several words why tempest tests is mostly performance tests for Ceilometer. The thing is that Ceilometer service is running during all other nova, cinder and so on tests run. All the tests create instances, volumes and each creation produces a lot of notifications. Each notification is the entry to database. So Ceilometer cannot process such a big amount of notifications quickly. Ceilometer tests have 'telemetry' prefix and it means that they will be started <span lang="en"><span>in the last turn. And it makes situation even worst.<br>
</span></span></div><span lang="en"><span>So my proposal:<br>1. create a non-voting job with Mongo-backend<br></span></span></div><span lang="en"><span>2. make sure that tests pass on Mongo<br>
</span></span></div><span lang="en"><span>3. merge tests to tempest but skip that on postgres and mysql till </span></span><br>bug/1291054 is resolved<br></div>4. make the new job 'voting'<br>
<br></div>The problem is only in Mongo installation. I have a cr <a href="https://review.openstack.org/#/c/81001/" target="_blank">https://review.openstack.org/#/c/81001/</a> that will allow us to install Mongo from deb. >From the other hand there is <a href="https://review.openstack.org/#/c/74889/" target="_blank">https://review.openstack.org/#/c/74889/</a> that enables UCA. I'm collaborating with infra-team to make the decision ASAP because AFAIU we need tempest tests in Icehouse (for more discussion you are welcome to thread [openstack-dev] Updating libvirt in gate jobs). <br>
<br></div>If you have any thoughts on this please share.<br></div><br>Thanks for attention,<br></div>Nadya<br><div><div><div><div><div><div><div><div><div><span lang="en"><span><br></span></span></div>
</div></div></div></div></div></div></div></div></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>