Re: Transaction support in Netconf

[Martin Bjorklund <mbj@tail-f.com>]

Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> wrote:
> Smart implementations may want to try to find a least disruptive
> transition from the current running configuration to the desired new
> configuration. So calculating the delta on the device might actually
> be a feature as this decouples the transition logic from the manager's
> instruction how to change the configuration. In other words, even if
> you ship a large edit config, it might internally make sense to create
> a temporary candidate configuration which is then committed (and you
> then calculate a least disruptive transition plan).
> 
> But note that I am talking "theory" here since I have not written my
> own netconf implementation. But if I were to do it, I would try to do
> things as outlined above. Perhaps others who have been working on
> implementations can say how they actually deal with this.

We handle this in the way you describe, both for edit-config and
copy-config.  But I guess it's better to discuss details off-line.


/martin

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