Re: [netmod] schema mount and YANG library

[Lou Berger <[e-mail]>]

On 1/17/2018 11:06 AM, Ladislav Lhotka wrote:
>>>> I thought that the problem with the current solution and NMDA, was that
>>>> there is no way to find out what the LNE schema is if the LNE isn't
>>>> booted, and hence isn't providing <operational>.  But I'm not sure what
>>>> issues that actually causes.  E.g. does it cause issues with
>>>> pre-configuration of the LNE?
>>> The issue that this causes is that the schema for the pre-configured LNE
>>> isn't
>>> known and validity of <intended> is unclear.
>> Please elaborate on what you see here as a problem.  Those working on
>> LNE's (including myself) don't see an issue here.
> Assume the "root" mount point for LNE is inline. Can you have a pre-provisioned
> configuration for a LNE entry? If so, then I assume there is no corresponding
> LNE entry in <operational>. If this is correct, then I don't see from where you
> get the embedded YL instance. That is, <intended> may contain
>
>    "ietf-logical-network-element:logical-network-element": [
>      { "name": "foo",
>        "root": { ... pre-provisioned config ... }
>      },
>      ...
>    ]
>
> But if the "foo" LNE isn't booted, then there is no "foo" entry in
> <operational>, i.e. also no corresponding instance of the "root" mount point.
>
> Is this reasoning flawed?
Yes.  At least the YL would be instantiated under operational because 
that's where it (server metadata) *always* goes.

Lou

>
> Lada
>