On Thu, Sep 25, 2014 at 08:44:01AM -0400, Thomas D. Nadeau wrote: > On Sep 25, 2014:8:36 AM, at 8:36 AM, Dean Bogdanovic <[email protected]> > wrote: > > Here is an example. The device supports x number of features and has a data > > model that represents the whole device. From that data model (schema), I > > decide to build a service that is using only parts of all available and > > store it into ephemeral DB, example L3VPN. Now in ephemeral only L3VPN > > service configurations will be stored. > > I2RS does not model the entire device; just its "routing system" > components.
While we're primarily concerned with I2RS semantics, the discussion has effectively broadened because the ephemeral mechanism we're discussing may be used by non-I2RS clients. I chatted with Dean a few minutes ago. I think much of the confusion regarding multiple ephemeral datastores is a result of a JUNOS implementation detail. He'll clarify the externally visible behavior which is more like what we've previously disucssed. -- Jeff _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
