On Tue, Jun 23, 2015 at 2:15 PM, Dean Bogdanovic <de...@juniper.net> wrote:
>
> On Jun 23, 2015, at 1:50 PM, Andy Bierman <a...@yumaworks.com> wrote:
>
>
>
>
>>
>> Yup, and reality can change when you swap FRUs.
>>
>> >> actual state + counters => operational state
>> >This should be:
>> > actual state + statistics => operational state
>> >Statistics is largely dominated by counters but not only counters.
>>
>> Sound good.
>>
>> Precise language is so important, so I think well-defined terms
>> matter. Then again, one can be completely precise while being
>> completely useless, like my current favorite word, sphygmomanometer.
>>
>>
> IMO getting the concepts right needs to be done first.
> Picking the right terms helps if the concepts are right in the first place.
>
> The thermometer example I have given many times needs to be understood.
>
> Let's say the same leaf "temperature" is used in all datastores.
> The "running" temperature is the configured desired value.
> The "operational" temperature is the current value read from a sensor.
>
> So where does "ephemeral" temperature fit in? Does this setting override
> the desired temperature and have no affect on the operational sensor value?
> Or does it over-write the sensor value to the device is now lying
> when it reports the operational temperature?
>
>
> Andy,
>
> ephemeral "temperature" would overwrite which ever data store was read
> to set "running" temperature. If the "temperature" was read from "startup"
> config, then ephemeral would mask the "temperature" leaf in the startup and
> running would read from ephemeral data store.
> One of the issues I personally ran into while at Juniper was people
> perception that configuration is persistent. Ephemeral config was very
> confusing to Juniper customers, as I was trying to explain them, that if
> they change the ephemeral and device reboots, the configuration is gone.
> For many of them, it was running config, but it is not. Another issue was
> no rollback. Actually, there is only rollback 0, which is done
> automatically by the system, if the config commit is not successful.
>
>
>
> IMO it is quite obvious that ephemeral data is configuration, not state.
>
>
> I would not say that ephemeral data is config. It is temporary state
> developers want to change the device state too.
>
>
Here is a simple example.
I hope it is not too abstract.
leaf admin-temp {
type uint32;
units "degrees Celsius";
description "The configured temperature.";
}
leaf oper-temp {
type uint32;
units "degrees Celsius";
config false;
description "The measured temperature.";
}
Would your I2RS solution be able to over-ride the admin-temp
with a temporary ephemeral value? Describe the solution
in detail. Provide all YANG and all protocol operations that
would be used
> Thx
>
> Dean
>
>
Andy
> Operational state is always read-only.
>
>
>
> Thanks,
>> Phil
>>
>
>
> Andy
>
>
>>
>> _______________________________________________
>> 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
>
>
>
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
