1 module odl-mdsal-lowlevel-target {
4 namespace "tag:opendaylight.org,2017:controller:yang:lowlevel:target";
7 import odl-mdsal-lowlevel-common {
8 revision-date "2017-02-15";
12 organization "OpenDaylight";
13 contact "Vratko Polak <vrpolak@cisco.com>";
14 description "Elements to test, which are not to be backed by any default implementation
15 upon feature installation.
16 See odl-mdsal-lowlevel-control (ll) for methods how to assign implementation in runtime.
17 This is separate module from odl-mdsal-lowlevel-control to simplify binding aware
18 implementation, which requires either all or no RPCs to be backed up by a single Java instance.";
20 revision "2017-02-15" {
21 description "Initial revision for Carbon clustering testing.";
25 description "Return the constant string provided by the previously registered implementation.
26 Propagate appropriate error if no, unreachable, or failing implementation is found.";
29 uses llc:constant-grouping;
33 rpc get-contexted-constant {
34 description "Return the constant corresponding to a registered implementation (either bound or default).
35 Propagate appropriate error if no, unreachable, or failing implementation is found.";
37 uses llc:context-grouping;
40 uses llc:constant-grouping;
44 rpc get-singleton-constant {
45 description "Return the constant string provided by the previously registered implementation.
46 Propagate appropriate error if no, unreachable, or failing implementation is found.
47 This is basically the same as get-constant, but it can have a different
48 implementation registered, thus allowing to track both implementations in longevity jobs.";
51 uses llc:constant-grouping;
55 notification id-sequence {
56 description "Notification where the publisher is identified by the id
57 and each publish increases the sequence number.";
59 leaf sequence-number {
60 description "Subscriber shall verify whether this value has increased
61 since the previous notification. The first sequence number published shall be 1.
62 Type is 64 bit to allow longevity tests, and signed to allow exceptional numbers.";
69 description "A list of integers nested in list of ids.
70 Ids are there to avoid OptimisticLockFailures from different writers.
71 Typical use of the int list is to generate data change notifications.
72 Config is true, in order to allow Restconf to reset content at will.
73 Expected writes should create and delete items at random, values 0 .. 2^20.";
79 description "Unsorted keyed list item. One write should create or delete up to one item.";
84 description "The integer value of this item.
85 Not range restricted, to allow more scenarios.";