On Wed, Sep 24, 2014 at 11:34:01AM -0400, Jeffrey Haas wrote: > On Wed, Sep 24, 2014 at 07:35:47AM -0400, Thomas D. Nadeau wrote: > > On Sep 24, 2014:3:10 AM, at 3:10 AM, Juergen Schoenwaelder > > <[email protected]> wrote: > [...] > > > > > > +-----------------+ > > > | | > > > +--- (+) ---+ | > > > ^ ^ v > > > +---+ +---+ +---+ > > > | | | | | | > > > |(1)| | | | | > > > | | | | | | > > > +---+ +---+ +---+ > > > > > > NC config ephemeral operational > > > datastore datastore state > > > > > > (1) The complete NC config datastore is at certain synchronization > > > points made persistent > > > > > > (+) Priority resolution, priorities may be per datastore or per > > > user or per 'application' or even per data node > > > > These are precisely the qualities I and some others were thinking of > > when we started i2rs. The idea is quite simple, as you have said above and > > really needs not be complicated more. > > It has its own complications. > > Do we permit more than one ephemeral datastore? If so, this simplifies data > object priority when resolving the operational state. But this also > complicates operational state integrity when you have multiple cross > references.
It complicates the merge operation - it does not affect the integrity of the operational state. But even that may not be true, at least not from the point of the merge algorithm. There likely is not much difference between merging 1 or N ephemeral datastores. And at the end of the day, if you have I2RS systems injecting conflicts, then it does not matter whether that happens in 1 ephemeral datastore and N ephemeral datastores. Having N ephemeral datastores had the advantage that I can easily disable a complete ephemeral datastore by modifying its priority while multiple I2RS systems writing concurrently into the same scratchpad will be much more fun to deal with. /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
