Data import / export is a new feature in master branch which can export datastore contents in JSON format and also import the same. Since this feature is not there in earlier releases and would not be usable for moving data from Be to Bo.
Regards Muthu From: controller-dev-boun...@lists.opendaylight.org [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Tom Pantelis Sent: Friday, March 24, 2017 4:13 PM To: Srini Seetharaman Cc: controller-dev@lists.opendaylight.org Subject: Re: [controller-dev] Backward compatibility of akka-persistence journal There isn't any cluster-admin RPCs to defined new shards and migrate data. You'd have to capture the data via REST from Beryllium and re-write it. There is also a data import/export project but I'm not really familiar with it. On Fri, Mar 24, 2017 at 1:06 AM, Srini Seetharaman <srini.seethara...@gmail.com<mailto:srini.seethara...@gmail.com>> wrote: > "instead of just relying on the default" - I assume you're referring to the > default shard. All yang modules for which there isn't a shard specified in > the .conf files are stored in the default shard. I suspect in your case the > previous journal backup had the yang module in question stored in the default > shard. However you had a specific shard defined in the .conf files so it went > to that shard to read the data. The data in the default shard still exists > and was restored but it just can't be accessed b/c reads/writes go to the > specific shard. Totally explains what I'm going through. Is there a way to port data over from my older Beryllium controller backup, which used the default shard, to my new Boron controller that uses module-specific shards? Can I perform the restore first, and then use the cluster-admin RPC to create the shards to move data over from the default to the module-specific shard?
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
