Re: [i2rs] Ephemeral State Requirements discussion

[Juergen Schoenwaelder <[e-mail]>]

On Tue, May 31, 2016 at 04:27:51PM -0400, Susan Hares wrote:
> Juergen: 
> 
> How does ephemeral sitting next to the <applied> data store provide
> the ability to augment configuration with ephemeral configuration or
> operational state with ephemeral operational state?

At the schema level, you will augment the schema tree. If the current
separation of /foo and /foo-state would go away, this will likely get
simpler (but this is orthogonal to the question how an <ephemeral>
datastore conceptually interacts with the other datastores).

At the data tree level, there is a magic merging (+) function involved
that takes configuration data from a configuration datastore and data
from an ephemeral data store and produces the resulting operational
state. The idea was to not further detail how this is achieved and
instead treat an ephemeral datastore pretty much like any other
control plane interface interacting with <operational state>.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <http://www.jacobs-university.de/>