Hi Kent, I am OK about requirements #12, #13 and #14 which I also further commented as follows:
#12 The <running> datastore contains the unexpanded template >That said, per #10<https://github.com/netmod-wg/template-reqs/issues/10>, it >may be possible to ask the device to return a expanded version of Yes, absolutely. In case of NMDA, this would be done by the client querying the intended datastore of the device Server In case of non-NMDA, the device would maintain a YANG state tree reflecting the data expanded, that can be queried by the client. #13: The <intended> datastore contains the expanded template Note that templates are also usable in non-NMDA devices: in a non-NMDA device, the device application software would expand the template in its private memory. This expanded data could be made visible to a YANG client by defining a state tree reflecting it. >The datastore is subject to validation, which means that all the templates >need to be expanded/flattened As commented in requirement #14, pre-validating a template might accelerate the validation of the expanded data #14: Off-box validation of <running> containing templates must be possible >Expectation is that clients would perform the template-expansion step prior to >using a validator (just like the servers do) Note also that since a template contains a configuration matching the one of a typical actual sub-bsystem (as defined in draft-rajaram-yang-config-template-framework-00), it could likely be pre-validated alone, prior being applied to actual sub-system. This "done-once-for-all" template validation might accelerate the validation of each sub-system expanded data ? Robert From: Kent Watsen <[email protected]> Sent: Sunday, December 1, 2024 8:21 PM To: Robert Peschi (Nokia) <[email protected]> Cc: [email protected] Subject: Re: [netmod] Mandatory/default statements and templates (was: Yang Template Proposals) CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information. Hi Robert, Just to clarify my point, I disagree with the idea that template mechanisms as introduced in Dublin could imply that the running data store contains the expanded data. The core problem discussed in Dublin is the large size of the configuration datastore (i.e. the running DS) that is passed by the Client to the Server. The primary goal of method#1 is to reduce the size of the running DS. I believe that method #2 has a similar goal, (and likely method 3, although there is no draft detailing it). A method that would expand data in the running datastore does not address this core problem (actually a draft would help clarifying what problem such a method addresses). Correct. I just added these two requirements: - https://github.com/netmod-wg/template-reqs/issues/12 - https://github.com/netmod-wg/template-reqs/issues/13 Good? > I suppose that a theory could be defined: a template is valid if its > expansion is valid Thoughts? About running DS validation, regardless of whether or not templates are used, my understanding is that whatever a client puts in the running datastore should ideally be validated before being pushed to a server. This is important to allow trustable pre-provisioning, i.e. a client having reasonable confidence that the server would not break when receiving the running DS. If the running DS contains a template, there should be no difference: ideally, the client should not send a configuration that is so broken that the device server would be unable to process it. Correct, I added this requirement: <https://github.com/netmod-wg/template-reqs/issues/14> https://github.com/netmod-wg/template-reqs/issues/14 - Robert Kent // contributor
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
