Hi, I've being reading this document: https://github.com/opendaylight/mdsal/blob/master/src/site/asciidoc/conceptual-data-tree.adoc
I have a few questions. 1) Very general question: Is the Conceptual Data Tree something new that is planned to get into ODL, or is it just an explanation of how the Data Stores are currently implemented? If it's new, when is it expected to get in? In the end of the document there is a description of DOMDataTreeProducer/Listener. Are these alternatives to the current DataTreeChangeListener? Or do they solve a different problem domain? 2) What is the difference between YangInstanceIdentifier and InstanceIdentifier? Is it related to different abstraction layers? 3) About this section: Federation, Replication and High Availability Support for various multi-node scenarios is a concern outside of core MD-SAL. If a particular scenario requires the shard layout to be replicated (either fully or partially), it is up to Shard providers to maintain an omnipresent service on each node, which in turn is responsible for dynamically registering DOMDataTreeShard instances with the Shard Registry service. Since the Shard Layout is strictly local to a particular OpenDaylight instance, an OpenDaylight cluster is not strictly consistent in its mapping of YangInstanceIdentifier to data. When a query for the entire data tree is executed, the returned result will vary between member instances based on the differences of their Shard Layouts. This allows each node to project its local operational details, as well as the partitioning of the data set being worked on based on workload and node availability. Partial symmetry of the conceptual data tree can still be maintained to the extent that a particular deployment requires. For example the Shard containing the OpenFlow topology can be configured to be registered on all cluster members, leading to queries into that topology returning consistent results. * I don't fully understand that part in bold. Can someone explain it using examples? * Regarding the last 2 sentences: What do you mean that a Shard can be registered on all cluster members? I thought that there is one Shard Leader per Shard, and the leader is the only one that manipulates the data and distributes it to all the other members, using the Raft algorithm. This approach provides the consistency, so I don't understand what do you mean here. 4) What is the maturity/roadmap of the support for different storage engines? Thanks, Guy Sela
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
