Subject: [netmod] opstate-reqs #4: Provide a tighter definition of "applied configuration"

From: Kent Watsen <[email-masked]>
Date: Wed, 30 Sep 2015 15:58:56 +0000

Again, let's tackle a hard issue before tomorrow's interim meeting - this time the definition of "applied configuration":

https://github.com/netmod-wg/opstate-reqs/issues/4

Currently, draft-chairs-netmod-opstate-reqs has this definition:

   o  applied configuration - this data represents the state that the
      network element is actually in, i.e., that which is currently
      being run by particular software modules (e.g., the BGP daemon),
      or other systems within the device (e.g., a secondary control-
      plane, or line card).

But, as Robert states in the issue:

    The definition of "applied configuration" is slightly vague, and there
    seems to be multiple interpretations of it on the WG alias, and
    hence a tighter specification of it would be useful.

    In particular:

      - does it include support for templating (as per openconfig-netmod-opstate-01 section 7.3.)?
      - is it allowed to represent system created objects that have no corresponding configuration?
      - how does it relate to the state of the system after a equivalent synchronous config commit (if at all)?

Already Mahesh and Einar have posted comments on the GitHub issue tracker.   Please first read the comments posted there and then continue the discussion here on the mailing list (not on the GitHub issue tracker).

PS: This issue is highly related to issue #5, which was also just opened for discussion on the mailing list.

Thanks,
Kent