HONEYCOMB-314: expose tag for tap and vlan interfaces

It is possible that interface creation for will succeed in VPP,
but Honeycomb crashes or request timeouts. In such situations, interface name
stored in Honeycomb's cache will not be updated. After restarting Honeycomb,
interface name will be generated.

In such cases Honeycomb user can use tag to identify interface.

Change-Id: I673c52e49dc788c761af471399d2ac839f62be04
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>

1 files changed, 13 insertions, 0 deletions

diff --git a/v3po/api/src/main/yang/v3po.yang b/v3po/api/src/main/yang/v3po.yang
index d1af6114c..828a095b0 100644
--- a/v3po/api/src/main/yang/v3po.yang
+++ b/v3po/api/src/main/yang/v3po.yang
@@ -257,12 +257,24 @@ module v3po {
     }
   }
 
+  grouping interface-tag {
+    leaf tag {
+      type string {
+        length 1..63;
+      }
+      description
+        "ASCII string placeholder for interface metadata. Value is stored in vpp,
+         and returned in read requests. No processing involved.";
+    }
+  }
+
   grouping tap-interface-base-attributes {
     leaf tap-name {
       type string{
         pattern "[a-zA-Z0-9\-;.+@$#^&*!_()=\[\]]*";
       }
     }
+    uses interface-tag;
   }
 
   grouping tap-interface-config-attributes {
@@ -335,6 +347,7 @@ module v3po {
       type vhost-user-role;
       default "server";
     }
+    uses interface-tag;
     description "vhost-user settings";
   }