So what you mean is that if I create a yang tree in a yang file, it will
ultimately translate into maximum two shards?
One for the operational and one for the configuration?
So for example elan.yang:
container elan-interface-forwarding-entries {
config false;
list elan-interface-mac {
key "elan-interface";
description "All the MAC addresses learned on a particular elan
interface";
max-elements "unbounded";
min-elements "0";
leaf elan-interface {
type leafref {
path "/if:interfaces/if:interface/if:name";
}
}
uses forwarding-entries;
}
}
container elan-tag-name-map {
config false;
list elan-tag-name {
key elan-tag;
leaf elan-tag {
type uint32;
}
leaf name {
type string;
description
"The name of the elan-instance.";
}
}
}
These 2 only live in the operational (Because config false), so it means 2
Shards ?
-----Original Message-----
From: Robert Varga [mailto:n...@hq.sk]
Sent: Wednesday, January 11, 2017 4:45 PM
To: Sela, Guy <guy.s...@hpe.com>; Tom Pantelis <tompante...@gmail.com>; Kochba,
Alon <alo...@hpe.com>
Cc: Williams, Marcus <marcus.willi...@intel.com>; Daniel Farrell
<dfarr...@redhat.com>; odl netvirt dev <netvirt-...@lists.opendaylight.org>;
controller-dev@lists.opendaylight.org; integration-...@lists.opendaylight.org
Subject: Re: [netvirt-dev] [controller-dev] [mdsal-dev] Netvirt Scale tests:
OutOfMemory from datastore
On 01/11/2017 03:42 PM, Sela, Guy wrote:
> I have some blurriness about what a shard is, that I still didn’t
> figure out.
>
> I have some guesses:
>
> 1) Every yang tree == one shard.
>
> 2) Shard can be a collection of a number of yang trees.
>
> 3) None of the above?
>
Mostly 1. Each shard encapsulates a single ShardDataTree, which encapsulates a
single DataTree. The sum of shards is presented as the data store (CDS).
Regards,
Robert
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev
