On 01/07/18 07:36, Ariel Adam wrote: > Robert, does this effect any existing DBs or external APIs? > Can you think of any possible back compatibility issues that should be > addressed?
Compatibility-wise, there are four aspects: 1) updated revision, meaning a datastore fixup is require during upgrade (i.e. via daexim) 2) generated binding package change (because of different revision), affects code interacting with these models in ODL 3) users populating the operational datastore need to populate it with non -state root prefix (see https://tools.ietf.org/html/rfc8343#section-1.1 and https://tools.ietf.org/html/rfc8344#section-1.1) 4) code dealing with backwards compatibility will have to suffer @Deprecated elements Points 1-3 are non-negotiable, they come from the model. Point 4 is up to projects to decide. Regards, Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev
