[bind10-dev] Planning for next sprint - input required

[Jerry Scharf]

Stephen,

I agree with all your comments.

Larissa and I started a survey for operational issues related to BIND 
10. Logging was mentioned by a number of people and I hope the followup 
of what these folks need to accomplish will provide insight into what 
problems they are addressing with logging. So many times people answer 
with the solution they think will work rather than explaining the 
problem they need to solve. It is only by getting to the problem that it 
is possible to compare possible solutions for best fit across the 
problem space.

It will be interesting to see if people are using logging to address 
problems that could benefit from more direct solutions. It's the tool 
they have so they try to make it do all the things they need.

One other interesting comment was about reasonable defaults for logging. 
Of course, different people will have different thoughts about what 
reasonable is, but it does indicate some thought should be given to 
defaults as well as functionality of logging.

jerry s

On 11/30/2010 4:17 AM, Stephen Morris wrote:
> On 30 Nov 2010, at 11:30, Jerry wrote:
>
>>> I agree, and in case you were not aware of it there's already a python
>>> version of logging framework for BIND 10 (src/lib/python/isc/log/).
>> Currently, the python logging framework only used by Xfrout module, there is
>> a need to apply logging in all other python modules.
> Agreed.
>
>>> For C++, there's a proposal of logging framework for boost
>>> (http://boost-log.sourceforge.net/), but it doesn't seem to be merged
>>> to the official boost libraries.  It also requires compiled library of
>>> boost (according to the documentation), so it's probably not suitable
>>> for us.  We could port BIND 9's logging framework, although this may
>>> be one of the areas where we don't like to take an in-house approach.
>> I am not sure if we should port BIND 9's logging framework, but at least
>> there are so many sexy features that we can learn from.
> There are many C++ logging frameworks.  Ones I've had a quick look at are:
>
> Google log (http://code.google.com/p/google-glog)
> Log4cpp (http://log4cpp.sourceforge.net)
> Log4cplus (http://log4cplus.sourceforge.net)
> Log4cxx (http://logging.apache.org)
> Pantheios (http://pantheios.sourceforge.net)
> Boost (http://boost-log.sourceforge.net)
>
> I think we should define our own requirements first, then make a selection.
>
> To minimise the dependency on external software we might want to define our own API and implement it in terms of a chosen package - that will make it simpler to switch if we want to do so in the future.
>
> Stephen
>
>
> _______________________________________________
> bind10-dev mailing list
> bind10-dev at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind10-dev