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
