On Thu, Nov 07, 2024 at 08:01:14AM +0000, Kent Watsen wrote: > > > I think it is important to keep the distinction between 'or:system' > > and 'sysds:system' since config generated by the system is different > > than config originating from a system datastore. > > I saw this comment last night and it didn’t sit right. > > Assume a server initially has no <system> datastore, and so reports a node’s > origin as “ds:system”. > > Then later supports the <system> datastore, trying to expose some of what it > does internally. Nothing has changed with the internal code, only the > datastore was created. Why should the node’s origin change?
For me, a valued copied from a datastore is different than a value generated by some program logic buried somewhere inside the system. I assume we have different understandings what a system datastore is all about, which then may be a bigger problem. > Regarding a value in <operational> varying from a value in <system>, > this just seems like a bug in the YANG defined for the <system> > datastore. For me, the origin indicates where I can find the source of a value. If the source is the system datastore, then I expect that to be reported and I expect to find the value also in the system datastore. If the source of the value is the system itself, then I expect that to be reported and I do not necessarily expect to find the value in the system datastore. I fear we may have a bigger problem by not agreeing on what the system datastore actually is... /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]
