On Mon, Dec 02, 2024 at 11:35:30AM +0000, maqiufang (A) wrote: > Hi, Jürgen, > > > > Although RFC 8342 avoids it, the problem remains in the real world: > > The client has the desire to reference system defined nodes, Must the > referenced system configuration always be copied to <running>? Does the > entire system-generated list entry need to be copied, or it is just the list > with at least the key? What if the system configuration changes and a stale > copy ends up in <running>?
The <running> datastore has to lead to a valid <intended>. A valid <intended> means that the configuration is valid, it does not mean that the configuration can all be applied. This is why we distinguish between <intended> and <applied> in the NMDA world. > How does the client overwrite a system-provided value? Or how to configure > the descendant nodes of system configuration? Is the copy needed? You configure the value. > Some system configurations are defined solely as a convenience (e.g., some > system provided policies), one of the objectives is to avoid re-creating > system configuration in <running>. > > I think the current design makes the interplay between system configuration > and client-provided configuration clear (e.g., allows <running> references > system config without requiring it to be copied into <running>). > So far, things like dangling references have been a no-go for a valid <running> aka <intended> datastore. /js -- Jürgen Schönwälder Constructor University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany _______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
