[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Difference between get and get-config



Johan Rydberg <johan.rydberg@edgeware.tv> wrote:
> Martin Bjorklund skrev:
> 
> >> Is this device state information read-only per defintion?  Or is it
> >> possible edit it (via <edit-config/>) if the agent supports the writable
> >> running capability?
> > 
> > <edit-config> modifies the configuration data only, not the state
> > data.  So from a <edit-config> perspective, the state data is
> > read-only.
> 
> Is the state data said to be part of the data model?

Yes.


> I'm trying to figure out what happen if the user pipes the data
> unmodifed from <get/> to <edit-config(replace)> and stores it in
> a configuration store.  As I see it there are three possible
> outcomes;
> 
>   1. the state data is filtered out.
>   2. the config and non-config data is stored in the store.
>   3. yields an error.

It is an error.  You will probably get an 'unknown-element' or
'unknown-attribute' error if you try to pass state data in an
<edit-config>.

> Also, should it be possible to <validate/> a document with state data?

No.  (Follows from the above).  Also note that the <validate> command
isn't very useful for validating documents, since you can't specify
the target db in <validate>.  So <validate> of a document can not do
much more than simple syntax checks.  There's an non-standard
extension that has been discussed on the list, which adds a
'test-only' <test-option> to <edit-config> that is useful for this
kind of validation.


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