On Sep 25, 2014, at 6:39 AM, Martin Bjorklund <m...@tail-f.com> wrote:
> Dean Bogdanovic <de...@juniper.net> wrote: >> >> On Sep 24, 2014, at 5:19 PM, Andy Bierman >> <a...@yumaworks.com<mailto:a...@yumaworks.com>> wrote: >> We can allow multiple ephemeral data stores, but the only dependency >> can be with the NC config datastore. Example: >> >> residential services >> business services >> >> >> >>> What does this really mean? >>> I did not understand the details at the interim. >>> Does this mean each datastore has separate data models? >> >> yes, each data store has separate data models > > Now I am confused. At the interim we agreed (and you argued for :) > that the schema (= data models) is the same for the config and > ephemeral datastore. 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. > > > >> I view it differently. In subscriber management different data models >> are used for residential and business subscribers. Some service data >> models can be very unique for business customers. > > Ok. > >> So separating them >> in different data stores makes sense, as they there are no overlaps >> with each other, only with NC config store. > > But since they are disjoint, there are really no reasons for not > keeping them in the same datastore, since there will be no conflicts. > >> In this case, we can get >> better performance. > > I can't see why, but this is probably an implementation issue. > > > /martin _______________________________________________ i2rs mailing list i2rs@ietf.org https://www.ietf.org/mailman/listinfo/i2rs
