Re: [I2rs-proto-dt] Minutes for 10/2/2015 meeting

[Jeffrey Haas <[e-mail]>]

On Mon, Oct 05, 2015 at 03:06:18PM -0700, Andy Bierman wrote:
> I am curious about bulk-read and bulk-write
> 
> IMO we just need 1 GET or 1 PUT type of method.
> Using YANG Patch with RESTCONF, multiple edits can be done at once.

That was my impression as well, but I had guessed that someone had brought
it up as a feature of some sort where I didn't have context.  

I suspect we can drop this section?

> It is important to decouple the produce (sensor) from the consumer (applied
> config)
> The sensor still puts out its operational value but the
> system (directed by I2RS edits) uses the injected value
> as the applied config instead of the sensor value.

I can grok your use of terminology, but it seems a bit skewed to how I'd
interpret things.

I'd like to suggest you put together the taxonomy section for the start of
the doc.  Or, if you think that the openconfig opstate draft covers it, we
can refer to that one.

> It is really just an implementation detail, but if N clients map
> to 1 priority (like the default priority if the client is not configured)
> then the client ID needs to be saved to decide first-1-wins in
> any future edit collisions.

Agreed.  I liked the idea mostly because it avoids having to adjudicate the
collisions.

> > I'm a bit confused by the writeable config false ephemeral true node.  Do
> > we
> > really want to support that?
> >
> 
> 
> That is the most controversial part.
> 
> Are there YANG objects that are config=false used to model
> the derived state?  Does that derived state ever need to
> be altered by I2RS?   An alternative would be to have new YANG objects
> that represent the I2RS-provided values.  But the config-stmt for
> these nodes needs some value.  Clearly it is not true, since NETCONF
> is not allowed to edit it.

My thoughts on this depend on the idea of datastores and schema.

Nodes are editable or not.  Whether the node has schema presence in
ephemeral or not is controlled by the ephemeral keyword in the yang.

It *may* be possible that a node is present in both config and in ephemeral
both. Examples are where we want to override things.

The question is how can we signal presence in both?  Do we want to simplify
and say that config datastore is always permitted when ephemeral is?

-- Jeff