Hi all, The discussions about dynamic datastores in I2RS today made me wonder about a scenario: What if a data model is supported in both conventional datastores and in a dynamic datastore (as well as being readable from the operational datastore), and the same list entry (e.g. interface abc, but with some different parms in the dynamic entry vs the config entry) has been created in both the running and the dynamic DS.
Only one of them can appear when reading the operational DS. I presume that it is up to the specification document of the dynamic DS to define the collision resolution between dynamic & conventional. But based on the revised DS draft I believe it would be necessary for the system to keep/store both copies of 'interface abc' so that a <get-data> with source=dynamic would return the dynamic version of interface abc while a <get-config> (or <get-data>) with source=running would return the conventional version of interface abc. Do I have that correct ? I think that also implies that removing one of the copies could cause the 're-installation' of the other (down to the app layer). This concept of storing multiple copies and re-installation is something I2RS wants to avoid. But since they have declared that their scope only includes the use of their models in the dynamic (ephemeral) DS, they won't have that behavior. Rgds, Jason
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
