Juregen and Jeff:
Can you define what a merge is? Could you define it using the example below
and another one? I know you have talked around the subject, but I need
another examples so I can adjust the drafts in progress with co-authors
(ISIS IM-DM, OSPF IM-DM, BGP IM-DM, PBR IM/DM) for i2rs.
Sue
============
list foo {
key id;
leaf id { type int32; }
leaf a { type int32; }
}
local config:
foo 42
In ephemeral config we now do SET /foo[id=42]/a to 4711. Thus, in
ephemeral we now have a single node (a) with value 4711.
-----Original Message-----
From: Juergen Schoenwaelder [mailto:[email protected]]
Sent: Thursday, September 25, 2014 2:25 AM
To: Jeffrey Haas
Cc: Thomas D. Nadeau; [email protected]; Susan Hares; [email protected]
Subject: Re: [i2rs] [netmod] Summary of discussion from netmod interim on
i2rs requirements on netmod/netconf
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
