Re: [netconf] Question about RFC8040 data root node and depth example

"Per Andersson (perander)" <perander@cisco.com> Thu, 07 May 2020 12:30 UTC

IronPort-PHdr: 9a23:DvRXNB+Mlr+oP/9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+7ZRCN6vBkjVuPVoLeuLpIiOvT5qbnX2FIoZOMq2sLf5EEURgZwd4XkAotDI/gawX7IffmYjZ8EJFEU1lorH6+OElRXs35Yg6arni79zVHHBL5OEJ8Lfj0HYiHicOx2qiy9pTfbh8OiiC6ZOZ5LQ69qkPascxFjA==
From: "Per Andersson (perander)" <perander@cisco.com>
To: Henning Rogge <hrogge@gmail.com>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] Question about RFC8040 data root node and depth example
Thread-Index: AQHWJD+yoUO+XWZSK0KzI7OByDeRIaicW8t6gAAdHACAABAUqA==
Date: Thu, 07 May 2020 12:30:36 +0000
Message-ID: <DM6PR11MB38186C2A41E4D9AFE9240A3BDBA50@DM6PR11MB3818.namprd11.prod.outlook.com>
References: <CAGnRvuqk6UnbZSr0GzHRfS4E5ORGTmPO=cY_KA9gAg=Nout50A@mail.gmail.com> <DM6PR11MB38183AC997EA6C633F2A0864DBA50@DM6PR11MB3818.namprd11.prod.outlook.com>, <CAGnRvuox=3F0eH89a0FBHy3Bz9eSH=gKwh0zH6sFhcyM0kRVPw@mail.gmail.com>
In-Reply-To: <CAGnRvuox=3F0eH89a0FBHy3Bz9eSH=gKwh0zH6sFhcyM0kRVPw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: a6c22029-7092-4b23-9427-08d7f28271f1
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 May 2020 12:30:36.5023 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: cJBZyNKg0wFZxsAdkb59RoP40tsn7mAvHQR3bZA0vLn7lr2id/KUo/JCOnvg0bQM1eudiph2+sZjq+SBeMoWcQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB2874
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/mIIi2da2rRcbQ9LPNuHDhlK-tgw>
Subject: Re: [netconf] Question about RFC8040 data root node and depth example
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 May 2020 12:30:44 -0000

> Henning Rogge <hrogge@gmail.com> on Thursday, May 7, 2020 13:14
>
>> Under the unified datastore (i.e. {+restconf}/data node), all top level
>> nodes would be found
>
> **sigh** I was worried to get this answer. My current implementation
> of the "yang data model" does load one library file... not a
> hierarchical series of libraries...
>
> This makes iterating over the "unified" datastore 'interesting',
> especially because of the depth/fields query parameter.
>
>> {
>>   "ietf-restconf:data": {
>>     "ietf-yang-library:yang-library": {},
>>     "example-jukebox:system": {},
>>     "example-jukebox:jukebox": {},
>>     "ietf-restconf-monitoring:restconf-state": {}
>> }
>
> In theory It should be possible to define the "data" YANG model and
> then import/augment everything from there, right?

The datastore resource "data" is not a model per say but a container
which should be populated with loaded models' top nodes.

Fom ietf-restconf.yang:

          container data {                                                                                         
            description                                                                                            
              "Container representing the datastore resource.                                                      
               Represents the conceptual root of all state data                                                    
               and configuration data supported by the server.                                                     
               The child nodes of this container can be any data                                                   
               resources that are defined as top-level data nodes                                                  
               from the YANG modules advertised by the server in                                                   
               the 'ietf-yang-library' module.";                                                                   
          }

See also RFC 8040 Section 3.4. Datastore Resource.


>> Note that example-jukebox have two top level nodes.
>
> I assume this is just your example, not the "example-jukebox" in the
> RFC 8040, right?

Yes, the example-jukebox.yang I referenced is probably from an earlier
RFC 8040 draft. But the principle is the same.


--
Per

[netconf] Question about RFC8040 data root node a… Henning Rogge
Re: [netconf] Question about RFC8040 data root no… Per Andersson (perander)
Re: [netconf] Question about RFC8040 data root no… Henning Rogge
Re: [netconf] Question about RFC8040 data root no… Per Andersson (perander)
Re: [netconf] Question about RFC8040 data root no… Henning Rogge