summaryrefslogtreecommitdiffstats
path: root/v3po/api
diff options
context:
space:
mode:
authorMaros Marsalek <mmarsale@cisco.com>2016-09-09 11:41:03 +0200
committerMaros Marsalek <mmarsale@cisco.com>2016-09-09 13:26:03 +0200
commitcd80707e4acb559db1207d94947d62be4a6655cf (patch)
tree486364636a287a35f5ca25175e516c2bb7749678 /v3po/api
parentd4b112b7058449da9b29313be9c8869bd254fad8 (diff)
HONEYCOMB-204 exclude deleted interfaces from operational data
Change-Id: I187ac52095e15c8c9302871a0d7e7be792e6a0e2 Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
Diffstat (limited to 'v3po/api')
-rw-r--r--v3po/api/src/main/yang/v3po-context.yang29
1 files changed, 29 insertions, 0 deletions
diff --git a/v3po/api/src/main/yang/v3po-context.yang b/v3po/api/src/main/yang/v3po-context.yang
new file mode 100644
index 000000000..ae35be5dd
--- /dev/null
+++ b/v3po/api/src/main/yang/v3po-context.yang
@@ -0,0 +1,29 @@
+module v3po-context {
+ yang-version 1;
+ namespace "urn:opendaylight:params:xml:ns:yang:v3po:context";
+ prefix "v3po-ctx";
+
+ revision "2016-09-09" {
+ description
+ "Initial revision of v3po specific context";
+ }
+
+ container disabled-interfaces {
+ config false;
+ // context data
+
+ description "Index list of disabled interfaces. VPP does not always delete an interface after deletion. It just
+ disables it and keeps it there. Honeycomb can hide such interfaces from operational data, and this
+ is the place to heep track of which interfaces were deleted, but are expected to show up in VPP";
+
+ list disabled-interface-index {
+
+ key "index";
+
+ leaf index {
+ type int32;
+ }
+ }
+ }
+
+} \ No newline at end of file