RE: More confirmed-commit issues

["Rob Enns" <rpe@juniper.net>]

>   1) add the "confirmed-commit-in-progress" warning I 
> proposed (or something like it) so other managers can 
> at least know their changes may be clobbered by the 
> agent at time T

This seems weak to me. The draft recommends that
the lock be held, in which case other managers couldn't make
changes during this window.

One could argue for similar warnings in the case of a shared 
candidate, or even a writable running configuration, given that 
multiple managers can be making changes simultaneously. In other
words, the automated restore that happens when an unconfirmed
commit is reverted is no more surprising than another manager
coming in and stomping on somebody's edits (candidate or not).
I think the best way to solve this is with the lock, not by
adding a warning message.

>   2) automatically revert the config if the "committing" session is 
> lost  (WG consensus for this already)

Change made.

>  3) automatically revert the config upon startup if the agent reboots 
> for any reason while a revert-timeout is pending

Change made.


Rob

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>