Hi Kent, My thinking was along the lines of what Jurgen mentions here: there are some values in operational that come from the system, but don't come from the system DS. I don't think the intention was that *anything* marked with origin "system" is also sitting there in the system DS.
My example of node "foo" having different values was between <running> and <operational> (nothing to do with system DS). In the current specs (without the new DS draft), do you agree the origin of foo would be "or:system"? I'm simply talking about a situation where the user asks for 1500 in the <running> but the server can't quite program that in the h/w due to some other constraints, or some rounding function, etc and can only do 1492 so that is what they report in <operational>. I don't think it makes sense for that leaf to suddenly now show up in the system DS. Jason > -----Original Message----- > From: Jürgen Schönwälder <[email protected]> > Sent: Thursday, November 7, 2024 4:02 AM > To: Kent Watsen <[email protected]> > Cc: Jason Sterne (Nokia) <[email protected]>; [email protected] > Subject: Re: [netmod] Re: origin "system" in system-config-09 > > > 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. > > > > 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]
