confirmed commit and locks

[Andy Bierman <abierman@cisco.com>]

Hi,

If session A does the following RPC sequence on the <candidate> target:

   lock
   edit-config +
   commit(confirmed-commit)
   unlock

Then session B does the following RPC sequence on the <candidate> target:

   lock
  --> code pt 1
   edit-config +
  --> code pt 2
   commit
  --> code pt 3
   unlock

 - What happens (at each code point) to session A if it tries to issue 
   the 2nd <commit>?
 - Is the rollback done if the timer pops on session A's confirmed commit?
 - Does session B's lock succeed?
 - Does session B's edit-config succeed?
 - Does session B's commit succeed?
 - What is the state of <candidate> at each code point if session A
   issues the 2nd commit or the rollback timer pops?

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