Subject: [netmod] syslog-model-03: list of syslog-selectors vs grouping used in-line

From: "Sterne, Jason (Jason)" <[email-masked]>
Date: Fri, 27 Mar 2015 00:26:55 +0000

Hi all,

The current model uses the syslog-selector 'in-line' inside each distributor/action object. Some implementations have a list of selector policies and then the distributors/actions reference a selector policy. It would be good if the model can somehow accommodate the latter. Here is a proposal:

Rename the grouping syslog-selector grouping to syslog-selector-parms.

Create a new grouping on top of the current syslog-selector:
    grouping syslog-selector {
        choice profile-or-inline {
            case inline {
                uses syslog-selector-parms;
            }
            case profile {
                ...leafref to a syslog-selector-profile...
            }
        }
    }

Add a syslog selector list:
    list syslog-selector-profile {
        key "syslog-sel-id";
        leaf syslog-sel-id {type uint16;}
        uses syslog-selector-parms;
    }

Having a list of syslog selectors is also nice for augmentations. You can't directly augment a grouping in YANG - you must augment an instance of where the grouping is used. When the grouping is inline in each syslog distributor/action you'd have to augment in each of those places to add something to the selector logic.

Regards,
Jason