Hi, just to clarify:
If you write to the running configuration datastore (e.g., via RESTCONF) and the running configuration datastore is locked, then the write is rejected. If there were a separate ephemeral datastore, then this ephemeral datastore may not have locks and there may be some form of a policy that controls how ephemeral content and running config datastore content is merged into what controls the behavior of the box. /js On Sun, Nov 16, 2014 at 05:55:31AM -0500, Joel M. Halpern wrote: > Thanks. It sounds like we will need to be careful with the structure of > what is being referenced so as not to run into locking issues. Most of > the suggestions I have heard make that sound doable. > > Yours, > Joel > > On 11/16/14, 1:09 AM, Kent Watsen wrote: > >Joel, > > > >RESTCONF will return 409 (Conflict) if a NETCONF datastore is locked. > > -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
