Re: More confirmed-commit issues

[Andy Bierman <ietf@andybierman.com>]

Andy Bierman wrote:

> Rob Enns wrote:
>
> > >  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.
> >  
>
> This is only true now that we will revert automatically if Mgr A 
> closes/loses
> its session.  It does rely on Mgr A doing everything correctly.  The 
> warning
> should not be issued often if everything goes as planned. It's a 
> warning not
> an error, so these operations still succeed.  IMO, it's more robust to
> warn Mgr B about this unique situation.


Another reason for the warning is that any manager can issue the 2nd 
<commit>,
even if that manager is actually intending to do its own "regular" commit.

I guess the warning isn't critical now that we've closed the 'dropped 
session'
and 'reboot' holes, and changed the timeout units from minutes to seconds,
so I'm not objecting to confirmed-commit anymore.  Now it takes misuse
to break things, instead of natural events like lost connections and 
reboots.

Andy


--
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/>