Andy, On Wed, Oct 01, 2014 at 11:15:40AM -0700, Andy Bierman wrote: > B) How are the same instances of the same data model related in the > running and ephemeral > datastores? > > I thought "phase 1" was supposed to be simple and the I2RS client would > just inject and remove > RIB data to override the running config. So, answer to (B) is: datastores > have independent > instances. If ephemeral instance exists, it is used. If deleted, then the > instance from the > running config (if any) becomes active. As long as the ephemeral instance > exists, the running config > instance is ignored.
I believe this to be the case. Discussion has suggested people aren't quite convinced in all cases. Working through the cases will hopefully push us to agreement. > Is this consistent with the architecture document? > Which solution best fits the agreed upon architecture? The architecture basically says state and user priority and client priority. It's abstract because we were requested to not argue architecture within the context of an underlying modeling language or protocol. Now that we've selected those, we have to figure out what reality we can live with. Much like any software engineering, architecture documents don't fully survive implementation. :-) -- Jeff _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
