Re: [netmod] schema mount and YANG library

[Ladislav Lhotka <[e-mail]>]

On Tue, 2017-12-19 at 10:05 +0100, Juergen Schoenwaelder wrote:
> On Tue, Dec 19, 2017 at 07:11:59AM +0100, Ladislav Lhotka wrote:
> > On Mon, 2017-12-18 at 15:30 -0500, Lou Berger wrote:
> > > lada,
> > > 
> > >     See below.
> > > 
> > > 
> > > On 12/15/2017 8:59 AM, Ladislav Lhotka wrote:
> > > > Hi,
> > > > 
> > > > unfortunately, using an action for querying embedded YANG library data
> > > > (needed for the "inline" case of schema mount) doesn't work either
> > > > because now under NMDA actions can be used only on instances in the
> > > > <operational> datastore.
> > > 
> > > but the inline/embedded library would (only) be present in the in the
> > > operational datastore, so what's the issue?
> > 
> > Well, the issue is described in my initial mail of this thread: the current
> > text
> > requires that every instance of an inline mount point contains the embedded
> > YANG library. Tha latter is state data, so the above requirement cannot be
> > satisfied if the mount point instance is in a configuration datastore.
> > 
> 
> Lada,
> 
> probably a stupid question (since I am not really familiar with the
> details of the mount work): What speaks against augmenting the yang
> library with a list of mount points and then mount point list elements
> can refer to the schema used at the mount point?

Absolutely, that's exactly what IMO needs to be done. All schemas, both top-
level and mounted, would then be contained in the YANG library's schema list.

I think the most sensible approach is to first agree on the new schema of YANG
library, and then define additional schema mount data as an augment.

Lada

> 
> /js
> 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67