On Thu, Jun 25, 2015 at 9:35 AM, Juergen Schoenwaelder < [email protected]> wrote:
> On Wed, Jun 24, 2015 at 06:24:25AM -0700, Andy Bierman wrote: > > > > 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. > > > > I do not understand the 'config ephemeral' on the left side. I think > it is the implementation (or its configuration) that decides which > data models also exist in the ephemeral data store. > > This is to allow for data that can only be edited in the ephemeral datastore instead of running or ephemeral datastore. It allows the XPath (and other rules) to be different than the existing rules for the running datastore. My slide did not go as far as Jeff wanted wrt/ allowing ephemeral data to reference operational data, but I think this would be OK. As Jeff pointed out, the ephemeral data does not exist until a controller creates it, unlike the persistent config that will be applied at boot-time before the operational state exists. /js > > Andy > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 <http://www.jacobs-university.de/> >
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
