Define/Clarify "fully synchronized" in "Requirement 1.D"

[rgwilton]

I think that it would be useful to define what "full synchronized" means.

In this context, I think of it as meaning if none of the configuration failed to be applied for any reason (e.g. due to absence of hardware, or internal system error).

[ggrammel]

The model I have in mind is the one of a harddisk: intended state is the write buffer, applied state is the drive, fully synchronized means that not only the data has been written to the disk, but also verified in a second step. i.e. read from the drive and compared to the write buffer. in other words: fully synchronized means the intended config is consistent, it has been applied to all necessary devices AND a successive verification process confirmed that both confis are matching

[kwatsen]

Moving issue to REVIEW state. On list, Kent writes:

All,

This issue somewhat dropped from our radar - we didn't discuss it 
during the interim or since.  Nonetheless, my interpretation of the 
below thread is that Robert's proposal was accepted.  So I'm going
to replace 1.D with the text below (albeit s/system/server/) and 
move this issue to the REVIEW state.

Thanks,
Kent

On 10/14/15, 2:08 PM, "Kent Watsen" <kwatsen@juniper.net> wrote:

The new 1-D works for me.  It is similar in spirit to the proposal I just
sent in the issue #4 thread.

Thanks,
Kent

On 10/13/15, 9:14 AM, "Robert Wilton" <rwilton@cisco.com> wrote:

In an attempt to try and close on some of the proposed requirement text
before Thursday's interim meeting.

Does anyone have any outstanding objections on using this proposed text
for Requirement 1.D, or is it sufficiently clear to update the draft,
and resolve issue 1?

OLD text for Requirement 1:

    1.  Ability to interact with both intended and applied configuration

        A.  The ability to ask the operational components of a system
            (e.g., line cards) for the configuration that they are
            currently using.  This is the "applied configuration".

        B.  Applied configuration is read-only

        C.  The data model for the applied configuration is the same as
            the data model for the intended configuration (same leaves)

        D.  For asynchronous systems, when fully synchronized, the data
            in the applied configuration is the same as the data in the
            intended configuration.

NEW text (as above, changing 1.D only):

    1.  Ability to interact with both intended and applied configuration

        A.  The ability to ask the operational components of a system
            (e.g., line cards) for the configuration that they are
            currently using.  This is the "applied configuration".

        B.  Applied configuration is read-only

        C.  The data model for the applied configuration is the same as
            the data model for the intended configuration (same leaves)

        D.  When the configuration change for any intended configuration
            node has been successfully applied to the system (e.g. not
            failed, nor deferred due to absent hardware) then the
            existence and value of the corresponding applied
            configuration node must match the intended configuration
            node.

Thanks,
Rob

[kwatsen]

new 1-D was accepted in -00 draft (moving to DONE)