[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Transaction support in Netconf
On Wed, Nov 16, 2005 at 09:16:03AM +0100, Balazs Lengyel wrote:
> Hello All,
> I am investigating transaction support in Netconf. One way to handle this
> is to use an edit-config operation with the test=test-then-set and
> error=rollback options. This however raises some questions as this
> functionality covers only a single RPC request:
> 1) How big can an RPC request be ? Any limit ?
I think the protocol does not specify a limit. However, concrete
implementations may have specific limits (after all, memory is usually
not unlimited).
> 2) If I have a big configuration tree is it allowed to modify to
> independent parts of the configuration tree in one RPC request
> (e.g. add a new interface and switch on and configure OSPF in on
> request) ?
I think the answer here is that this is specifically allowed.
The other option to address your requirement is to use the candidate
capability. This allows to make multiple changes on a scratchpad
configuration and once you are done with your changes, you commit the
candidate configuration in a single commit operation. I believe this
is actually better than trying to create a large atomic edit-config
transaction. (So make sure the netconf implementations you are looking
at support the candidate capability.)
/js
--
Juergen Schoenwaelder International University Bremen
<http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany
--
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/>