Hello Michael, we discussed the items you have put on today's Kernel Projects' Call agenda.
> Stephen & Michael: Follow-up to sharding breakout session at DDF > > How to have a single shard for operational and config, but with/without > persistence? This is not possible. Operation and Configuration data stores are always separate instances of a DataTree. Note that the ability to perform atomic commits across both config and oper data stores is going away as per the requirements and feedback gathered during the design of Conceptual Data Tree. See https://lists.opendaylight.org/pipermail/controller-dev/2016-April/011798.html for details. > How to control shard leader election, to force separate operational and > config shard to be on the same node? > Could we use the make-leader-local RPC for this, and how? Yes, and I do believe CSIT does this. As for coordinated shard failover control, there is no provision to do this within CDS. > Anyone has any objections to a Gerrit changing (upstream's) default shard > configuration file to 1 shard? Is there a particular reason to do this? I think we wanted to have this to make it obvious that topology and inventory are distinct... Thanks, Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
