Hi,
thanks.
A few details of the solution I am working on...
1) defaults are not used in the ephemeral datastore
The default-stmt is altered for the ephemeral datastore.
Default leafs are ignored (except for XPath evaluation).
Otherwise the schema default would always override the configuration.
2) XPath hierarchy is based on config-stmt.
config=true context node -> can reference config=true
config=ephemeral context node -> can reference true + ephemeral
config=false context node -> can reference true, ephemeral, false
3) must/when evaluation applies only to the datastore indicated by
config-stmt
config=true -> running
config=ephemeral -> ephemeral
config=false -> operational
4) panes of glass applied to data instances
all running datastore instances are visible in the ephemeral datastore
all ephemeral datastore instances are visible in the operational
datastore
5) admin-foo and oper-foo can go away
The instance of 'admin-temp' in the operational datastore would return
the value in effect, not the desired value, so 'oper-temp' is not needed
and the correlation between config, ephemeral, and operational is
maintained
in the common instance-identifier in all 3 datastores
Andy
On Wed, Jun 24, 2015 at 6:28 AM, Joel M. Halpern <[email protected]>
wrote:
> The separations and effects shown there match my understanding.
> Thank you,
> Joel
>
> On 6/24/15 9:24 AM, Andy Bierman wrote:
>
>> Hi,
>>
>> I prepared 1 slide (based on Kent's slide).
>> I am trying to understand the types of data
>> and how they are identified in YANG and conceptually
>> separated for protocol access.
>>
>>
>>
>> Andy
>>
>>
>>
>> _______________________________________________
>> netmod mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/netmod
>>
>>
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
