Re: [netmod] Syslog YANG Model Presentation

["Clyde Wildes (cwildes)" <[e-mail]>]

Juergen,

We will update the description for global-logging to be clear.

We will consider adding syslog listener configuration as a feature.

We will update the reference section in the model as you described.

Thanks,

Clyde


On 7/23/14, 6:03 PM, "Juergen Schoenwaelder"
<[e-mail]> wrote:

>On Wed, Jul 23, 2014 at 08:40:11PM +0000, Clyde Wildes (cwildes) wrote:
>> >
>> >PS: I do not really understand 'global logging'.
>> 
>> [clyde] Some vendors include an extra log message suppression mechanism
>> that is logically before the selectors/actions mechanism. We called this
>> mechanism ³global-logging². It is listed as a feature for those vendors
>> that support it and it is described in the RFC document.
>
>If this is a global filter, it should probably have a name that makes
>this clearer. But then, the I-D also says:
>
>  feature global-logging {
>    description
>      "This feature represents the ability to adjust
>       log message severity per logging facility on the
>       global level.";
>  }
>
>This says 'adjust severity' which is again different from suppression
>or filtering. The data model uses the facility-logging grouping, which
>then again reads as a filter. In other words, it seems like messages
>not passing 'global-logging' will be dropped. If this is the
>intention, please make sure this is clearly described.
>
>> >PS: A configuration model should probably also include ways to
>> >    configure on which endpoints the syslog 'daemon' is receiving
>> >    input.
>> 
>> [clyde] This model does not include syslogd daemon listener
>>configuration
>> (the daemon listens for syslog messages on port 514 on all interfaces if
>> the ³-r² switch is included on the syslogd command line). I am thinking
>> that syslog daemon configuration should be a separate model since this
>> model is concerned with syslog message distribution. For reference here
>>is
>> the FreeBSD syslogd man page which shows the many syslogd daemon
>>options:
>> http://www.freebsd.org/cgi/man.cgi?query=syslogd&sektion=8
>
>Listener configuration could be left out or it could be made a
>feature; most open source syslog daemons can listen for incoming
>messages.
>
>> >PS: The reference in the revision statement is usually used to refer
>> >    to the document defining that specific revision of the data model.
>> >
>> >PS: For the example, simple show the config instance not the NETCONF
>> >    exchange.
>> 
>> [clyde] Please explain. Should the reference for revision 02 be to:
>>         http://tools.ietf.org/html/draft-wildes-netmod-syslog-model-02
>> 
>> The current revision 03 contents are:
>> 
>>  revision 2014-06-10 {
>>    description
>>      "Initial revision.";
>>    reference
>>      "This model references RFC 5424 - The Syslog Protocol.";
>>   }
>> 
>
>The idea is to refer to the document defining the YANG module, e.g.:
>
>     // RFC Ed.: update the date below with the date of RFC publication
>     // and remove this note.
>     revision 2014-06-10 {
>       description
>         "Initial revision.";
>       reference
>         "RFC XXXX: A YANG Data Model for SYSLOG";
>     }
>
>This way, someone who has the YANG module can easily find the RFC
>defining it.
>
>/js
>
>-- 
>Juergen Schoenwaelder           Jacobs University Bremen gGmbH
>Phone: [phone]         Campus Ring 1, 28759 Bremen, Germany
>Fax:   [phone]         <http://www.jacobs-university.de/>