HONEYCOMB-290 - Revert of presence removal

Presence is actually needed here, otherwise both mandatory
leafs(table-id under vrf-subtable and bridge-domain-ref under
bridge-domain-subtable) are required, which is unnecessary
because sub-tables can be defined in any combination(none,one,both)

This will recreate bug described in HONEYCOMB-290 till
https://git.opendaylight.org/gerrit/#/c/48532/ is merged.
In the mean time, whole subtree request must be used

Change-Id: Id160888ea4b3e452288ce2d42d589dcc5319dd49
Signed-off-by: Jan Srnicek <[email protected]>

diff --git a/lisp/api/src/main/yang/lisp.yang b/lisp/api/src/main/yang/lisp.yang
index 5d2092c..f104bd8 100755 (executable)
--- a/lisp/api/src/main/yang/lisp.yang
+++ b/lisp/api/src/main/yang/lisp.yang
@@ -249,6 +249,7 @@ module lisp {
             description "vni";
         }
         container vrf-subtable {
+          presence "Enable L3 mapping";
           leaf table-id {
              type uint32;
              description "table-id";
@@ -259,6 +260,7 @@ module lisp {
           description "VRF subtable";
         }
         container bridge-domain-subtable {
+          presence "Enable L2 mapping";
           leaf bridge-domain-ref {
             type string;
             description "Name reference to existing bridge domain";