On 10/22/2013 10:19 AM, Sean Dague wrote:
On 10/21/2013 10:27 AM, Neal, Phil wrote:
Sean, we currently have a BP out there to investigate basic tempest
integration and I think this might fall under the same umbrella.
Unfortunately I've not been able to free up my development time
for it, but I've assigned it out to someone who can take a look and
report back.
https://blueprints.launchpad.net/tempest/+spec/basic-tempest-integration-for-ceilometer
This is kind of worse than tempest integration issues. As far as I can
tell ceilometer via devstack is basically non functional at all. And
sort of worse than non functional, it's spewing errors, a lot.
This really ought to be a top ceilometer item to address, otherwise we
should probably turn off celiometer in devstack by default, because
it's really not working at the moment.
-Sean
Here are the two errors showing up persistently that are not
whitelisted. Such log errors are now being shown in the console log
right after the tempest tests finish.
https://bugs.launchpad.net/ceilometer/+bug/1243251
2013-10-21 21:11:00.229 | 2013-10-21 21:05:20.046 5624 ERROR
ceilometer.collector.dispatcher.database [-] Failed to record metering
data: QueuePool limit of size 5 overflow 10 reached, connection timed
out, timeout 30
https://bugs.launchpad.net/ceilometer/+bug/1243249
2013-10-21 20:22:27.600 | Log File: ceilometer-alarm-evaluator
2013-10-21 20:22:27.600 | 2013-10-21 20:14:33.038 22760 ERROR
ceilometer.alarm.service [-] alarm evaluation cycle failed
See also https://bugs.launchpad.net/ceilometer/+bug/1237671
-David
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
