RE: partial locking

["David Harrington" <ietfdbh@comcast.net>]

> -----Original Message-----
> From: Andy Bierman [mailto:ietf@andybierman.com] 
[...]
> 
> This may be true in the abstract sense, but for standards purposes,
> I am interested in how the NETCONF protocol operations work with
> the XML encoded data in the <config> element.  

But I'm interested in how the 'lock' works, which seems to be
potentially larger than the view encoded in XML.

>From RFC4741:

   o  Running: The complete configuration currently active on the
      network device.  Only one configuration datastore of this type
      exists on the device, and it is always present.  NETCONF
protocol
      operations refer to this datastore using the <running> element.

and

      The lock operation allows the client to lock the configuration
      system of a device.  Such locks are intended to be short-lived
and
      allow a client to make a change without fear of interaction with
      other NETCONF clients, non-NETCONF clients (e.g., SNMP and
command
      line interface (CLI) scripts), and human users.
	...
      The lock operation takes a mandatory parameter, target.  The
      target parameter names the configuration that will be locked.
      When a lock is active, using the <edit-config> operation on the
      locked configuration and using the locked configuration as a
      target of the <copy-config> operation will be disallowed by any
      other NETCONF session.  Additionally, the system will ensure
that
      these locked configuration resources will not be modified by
other
      non-NETCONF management operations such as SNMP and CLI. 

When you talk about a Netconf global lock, on an implementation that
has a "running config" that is "the complete configuration currently
active on the network device",  does the global lock apply only to the
Netconf XML-encoded subset of the implementation's running config?

If I have multiple virtual routers within a physical router, then does
a Netconf lock on "running" only apply to the configuration of one
virutal router or to "the complete configuration currently active on
the network device"?

If I parse your paragraph correctly, you are saying "the XML encoded
data in the <config> element" + "may or may not represent the entire
device." Doesn't that contradict the definition of <running> in
RFC4741?

dbh




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