[openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

Nadya Privalova nprivalova at mirantis.com
Tue Mar 18 12:09:12 UTC 2014

Hi folks,

I'd like to discuss Ceilometer's tempest situation with you.
Now we have several patch sets on review that test core functionality of
Ceilometer: notificaton and pollstering (topic
But there is a problem: Ceilometer performance is very poor on mysql and
postgresql because of the bug
https://bugs.launchpad.net/ceilometer/+bug/1291054. Mongo behaves much
better even in single thread and I hope that it's performance will be
enough to successfully run Ceilometer tempest tests.
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 in the last turn. And it
makes situation even worst.
So my proposal:
1. create a non-voting job with Mongo-backend
2. make sure that tests pass on Mongo
3. merge tests to tempest but skip that on postgres and mysql till
bug/1291054 is resolved
4. make the new job 'voting'

The problem is only in Mongo installation. I have a cr
https://review.openstack.org/#/c/81001/ that will allow us to install Mongo
from deb. From the other hand there is
https://review.openstack.org/#/c/74889/ 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).

If you have any thoughts on this please share.

Thanks for attention,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140318/0632a57d/attachment.html>

More information about the OpenStack-dev mailing list