Lisp initialization

Changes
 - Lisp state excluded from config data(bug introduced during L2 support patch)
 - Initializing for every read customizer
 - Proper rebinding of paths from LispState on Lisp

Change-Id: I3da821412313e0826e5d80fdccfdc1021a550ad5
Signed-off-by: Jan Srnicek <jsrnicek@cisco.com>

1 files changed, 5 insertions, 1 deletions

diff --git a/lisp/api/src/main/yang/lisp.yang b/lisp/api/src/main/yang/lisp.yang
index f104bd84e..933211c79 100755
--- a/lisp/api/src/main/yang/lisp.yang
+++ b/lisp/api/src/main/yang/lisp.yang
@@ -23,6 +23,10 @@ module lisp {
     "This YANG module defines the generic configuration and
     operational data for LISP in VPP";
 
+  revision 2017-03-15 {
+    description "Excludes lisp-state from config data";
+  }
+
   revision 2016-12-14 {
     description
      "This revision adds support for L2 features, by adding vrf-subtable/bridge-domain-subtable
@@ -341,7 +345,7 @@ module lisp {
   }
 
   container lisp-state {
-
+    config "false";
     // lisp_enable_disable / lisp_enable_disable_status_dump
     leaf enable {
       type boolean;