Hi Rohit,
On 29/05/2018 10:35, Rohit R Ranade wrote:
No need for the deviations for <running>. <running> only contains the "config true" parts of the schema.Hi All, Consider the below YANG tree, which contains both “rw” and “ro” nodes. module: ietf-interfaces +--rw interfaces | +--rw interface* [name] | +--rw name string | +--rw description? string | +--rw type identityref | +--rw enabled? boolean | +--rw link-up-down-trap-enable? enumeration {if-mib}? | +--ro admin-status enumeration {if-mib}? | +--ro oper-status enumeration | +--ro last-change? yang:date-and-time | +--ro if-index int32 {if-mib}? | +--ro phys-address? yang:phys-address | +--ro higher-layer-if* interface-refFrom what I understand, in the new yang-library structure the schema for <operational> data-store will have the complete YANG tree. The schema for <running> will need to add deviations with “not-supported” for all the “ro” nodes for this module ?
So, for a normal, NMDA compliant server, the same schema can be used for all datastores.
Thanks, Rob
With Regards, Rohit R Ranade _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
