[Openstack] Service debug settings / white-/blacklist for debug messages

Uwe Sauter uwe.sauter.de at gmail.com
Thu Feb 19 12:32:54 UTC 2015


Hi all,

Example is for nova but I think this is eligible for every OpenStack service.

Currently I have "debug = True" in nova.conf which creates a lot of semaphore messages like:

2015-02-19 13:15:15.780 3796 DEBUG nova.openstack.common.lockutils [req-f0eb99db-a4a4-475c-b154-281bc1348b2c ] Created new
semaphore "compute_resources" internal_lock /usr/lib/python2.7/site-packages/nova/openstack/common/lockutils.py:206
2015-02-19 13:15:15.780 3796 DEBUG nova.openstack.common.lockutils [req-f0eb99db-a4a4-475c-b154-281bc1348b2c ] Acquired semaphore
"compute_resources" lock /usr/lib/python2.7/site-packages/nova/openstack/common/lockutils.py:229
2015-02-19 13:15:15.781 3796 DEBUG nova.openstack.common.lockutils [req-f0eb99db-a4a4-475c-b154-281bc1348b2c ] Got semaphore /
lock "update_usage" inner /usr/lib/python2.7/site-packages/nova/openstack/common/lockutils.py:271
2015-02-19 13:15:15.781 3796 DEBUG nova.openstack.common.lockutils [req-f0eb99db-a4a4-475c-b154-281bc1348b2c ] Releasing semaphore
"compute_resources" lock /usr/lib/python2.7/site-packages/nova/openstack/common/lockutils.py:238
2015-02-19 13:15:15.781 3796 DEBUG nova.openstack.common.lockutils [req-f0eb99db-a4a4-475c-b154-281bc1348b2c ] Semaphore / lock
released "update_usage" inner /usr/lib/python2.7/site-packages/nova/openstack/common/lockutils.py:275
2015-02-19 13:15:15.908 3796 DEBUG nova.openstack.common.lockutils [req-f0eb99db-a4a4-475c-b154-281bc1348b2c ] Releasing semaphore
"3a8dadf8-4713-487f-b6a6-1836d5f961a0" lock /usr/lib/python2.7/site-packages/nova/openstack/common/lockutils.py:238
2015-02-19 13:15:15.908 3796 DEBUG nova.openstack.common.lockutils [req-f0eb99db-a4a4-475c-b154-281bc1348b2c ] Semaphore / lock
released "do_terminate_instance" inner /usr/lib/python2.7/site-packages/nova/openstack/common/lockutils.py:275


This kind of message doesn't help me to debug why an instance won't start as those messages are so many that the important stuff
is hidden in between.

So is there a mechanism to select specific debug messages (whitelist) or better to disable only those that I don't want to see
(blacklist, e.g. everything originating from nova.openstack.common.lockutils). The current situation I know is that I can debug
messages either on or off…

Regards,

	Uwe




More information about the Openstack mailing list