On Wed, Jan 25, 2017 at 11:05 AM, Juergen Schoenwaelder < [email protected]> wrote:
> Just search for ephemeral in the document and you will hit this: > > The model foresees control-plane datastores that are by definition > not part of the persistent configuration of a device. In some > contexts, these have been termed ephemeral datastores since the > information is ephemeral, i.e., lost upon reboot. The control-plane > datastores interact with the rest of the system through the <applied> > or <operational-state> datastores, depending on the type of data they > contain. Note that the ephemeral datastore discussed in I2RS > documents maps to a control-plane datastore in the revised datastore > model described here. > > The modules in draft-ietf-i2rs-yang-l3-topology-08 and draft-ietf-i2rs-yang-network-topo-10 appear to contain only configuration data nodes. They are mandatory to implement. >From RFC 7950: 7.21.1. The "config" Statement The "config" statement takes as an argument the string "true" or "false". If "config" is "true", the definition represents configuration. Data nodes representing configuration are part of configuration datastores. If "config" is "false", the definition represents state data. Data nodes representing state data are not part of configuration datastores. If these nodes are not intended to be part of configuration datastores, then the nodes need to marked as "config false". > /js > > Andy > On Wed, Jan 25, 2017 at 01:58:13PM -0500, Susan Hares wrote: > > Juergen: > > > > Where do you think the revised data store model in that draft suggests > ephemeral data stores live? > > > > Sue > > > > -----Original Message----- > > From: i2rs [mailto:[email protected]] On Behalf Of Juergen > Schoenwaelder > > Sent: Wednesday, January 25, 2017 1:54 PM > > To: Susan Hares > > Cc: [email protected]; [email protected]; 'Alia > Atlas'; 'Giles Heron'; [email protected]; 'Lou Berger' > > Subject: Re: [i2rs] Kathleen Moriarty's No Objection on > draft-ietf-i2rs-yang-l3-topology-08: (with COMMENT) > > > > Sue, > > > > the current thinking is documented in > > draft-ietf-netmod-revised-datastores-00.txt. > > > > /js > > > > On Wed, Jan 25, 2017 at 12:52:47PM -0500, Susan Hares wrote: > > > Juergen: > > > > > > "And with the revised datastore model it will also be straight forward > to have an implementation that just exposes topological data via the > operational state datastore. And the revised datastore model also paves > the path to support datastores that can also inject ephemeral data." > > > > > > Where do you believe the revised data store model suggest ephemeral > data can be injected - (?written)? > > > > > > Sue > > > > > > -----Original Message----- > > > From: i2rs [mailto:[email protected]] On Behalf Of Juergen > > > Schoenwaelder > > > Sent: Wednesday, January 25, 2017 10:33 AM > > > To: Giles Heron > > > Cc: [email protected]; [email protected]; Lou > > > Berger; [email protected]; Alia Atlas > > > Subject: Re: [i2rs] Kathleen Moriarty's No Objection on > > > draft-ietf-i2rs-yang-l3-topology-08: (with COMMENT) > > > > > > On Wed, Jan 25, 2017 at 03:19:58PM +0000, Giles Heron wrote: > > > > > > > > > On 25 Jan 2017, at 15:18, Juergen Schoenwaelder < > [email protected]> wrote: > > > > > > > > > > On Wed, Jan 25, 2017 at 10:07:45AM -0500, Alia Atlas wrote: > > > > >> > > > > >> So - if one has models - such as a writable topology - where > > > > >> there can be dependencies on dynamic data, then those models > > > > >> can't be in the configuration data-store as currently defined. > > > > >> > > > > > > > > > > Yes > > > > > > > > but isn’t this confusing models and implementation? > > > > > > I just confirmed that the old datastore model does not support > writable ephemeral datastores. No more no less. And there is work in NETMOD > (and NETCONF) to revise the datastore model and to make data model reuse in > different datastores even simpler. > > > > > > > if you have a case where you have a dependency on dynamic data then > you can’t put that instantiation of the model in the configuration > data-store. > > > > > > > > but if your implementation never depends on dynamic data then it > ought to be fine. > > > > > > Yes. This should be fine. > > > > > > And with the revised datastore model it will also be straight forward > to have an implementation that just exposes topological data via the > operational state datastore. And the revised datastore model also paves > the path to support datastores that can also inject ephemeral data. > > > > > > /js > > > > > > -- > > > 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/> > > > > > > _______________________________________________ > > > i2rs mailing list > > > [email protected] > > > https://www.ietf.org/mailman/listinfo/i2rs > > > > > > > -- > > 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/> > > > > _______________________________________________ > > i2rs mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/i2rs > > > > -- > 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/> > > _______________________________________________ > i2rs mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i2rs >
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
