Open Stack

On 01/15/2014 10:13 AM, David Kranz wrote:
> On 01/15/2014 11:56 AM, Steven Dake wrote:
>> Hi,
>>
>> Ken'ichi Omichi submitted a change [1] in devstack to change the 
>> default log level to 1 for libvirt.  This results in continual spam 
>> to /var/log/messages in my development system, even after exiting 
>> devstack.  The spam looks like:
>> "
>> Jan 14 08:13:49 bigiron libvirtd: 2014-01-14 15:13:49.334+0000: 1480: 
>> debug : virFileClose:90 : Closed fd 8
>> Jan 14 08:13:49 bigiron libvirtd: 2014-01-14 15:13:49.334+0000: 1480: 
>> debug : virFileClose:90 : Closed fd 9
>> Jan 14 08:13:49 bigiron libvirtd: 2014-01-14 15:13:49.334+0000: 1480: 
>> debug : virFileClose:90 : Closed fd 10
>> Jan 14 08:13:49 bigiron libvirtd: 2014-01-14 15:13:49.334+0000: 1480: 
>> debug : virFileClose:90 : Closed fd 11
>> "
>> in a continual loop
>>
>> I submitted a change [2] that sets the default to level 2 (info + 
>> warnings + errors) which was -1'ed by Sean Dague.  His suggestion was 
>> to take the discussion upstream so consensus around what the default 
>> should be can be made so this doesn't end up getting changed every week.
>>
>> The core mission of devstack is to provide a development environment 
>> for developers.  The fact that it is being used in the gate seems 
>> somewhat ancillary to it's mission, and forcing a default of "spam 
>> the system logs with tons of libvirt messages" seems counter to the 
>> core mission of devstack.  As is, without modification devstack makes 
>> looking at anything useful in my system logs impossible without grep 
>> -v libvirt and is intrusive to developer's workstations.
>>
>> [1] https://review.openstack.org/#/c/63992/ 
>> <https://review.openstack.org/#/c/63992/>
>> [2] https://review.openstack.org/#/c/66630/
> Why not just make this a shell variable/localrc option that defaults 
> to the original and have the gate jobs set it to debug?
>
David,

I don't think devstack should be mucking with system config files 
including libvirt in the default case.  If someone wants to propose a 
special case change to handle the gate jobs, that would solve the gate 
not having enough log information, as indicated in a followup thread 
from Daniel.  Since the gate jobs are throw-away VMs, the problem of 
polluting developer workstation config files with devstack changes 
doesn't exist.

Regards
-steve

>  -David
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140115/1b9d615b/attachment.html>