diff options
author | 2016-06-10 07:36:43 +0200 | |
---|---|---|
committer | 2016-06-10 08:03:58 +0000 | |
commit | 70e243d1c48f9554bd4e28e80f7ff766db6fe857 (patch) | |
tree | 6c2f91854470d0e61f267ee05ea3067b34e05629 /vbd/api/src/main/yang/vbridge-topology.yang | |
parent | 973d8c2ecbb02cf6e4971060b6edec3617bce96f (diff) |
HONEYCOMB-7: Remove VBD form HC
VBD is now subproject of ODL:
https://git.opendaylight.org/gerrit/#/admin/projects/honeycomb/vbd
Change-Id: I1bf01a01cca50fe5e3f4f82a53c6b15ec5c7091d
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
Diffstat (limited to 'vbd/api/src/main/yang/vbridge-topology.yang')
-rw-r--r-- | vbd/api/src/main/yang/vbridge-topology.yang | 165 |
1 files changed, 0 insertions, 165 deletions
diff --git a/vbd/api/src/main/yang/vbridge-topology.yang b/vbd/api/src/main/yang/vbridge-topology.yang deleted file mode 100644 index 954982f24..000000000 --- a/vbd/api/src/main/yang/vbridge-topology.yang +++ /dev/null @@ -1,165 +0,0 @@ -module vbridge-topology { - // vi: set et smarttab sw=4 tabstop=4: - - yang-version 1; - namespace "urn:opendaylight:params:xml:ns:yang:vbridge:topology"; - prefix "vbridge"; - - organization "Cisco Systems, Inc."; - - contact "Robert Varga <rovarga@cisco.com>"; - - description - "Base model describing a virtual bridge domain mapped expressed - as a network topology. Implementations of this model are expected - to map this topology onto an underlay transport/managent topology, - such as a NETCONF topology talking to forwarding boxes - - Copyright (c) 2015 Cisco and/or its affiliates. - - Licensed under the Apache License, Version 2.0 (the \"License\"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at: - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an \"AS IS\" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License."; - - revision "2016-01-29" { - description "Initial cut"; - } - - import ietf-inet-types { prefix "inet"; } - import network-topology { prefix nt; revision-date 2013-10-21; } - import odl-external-reference { prefix extref; } - import v3po { prefix "v3po"; } - import yang-ext { prefix ext; revision-date "2013-07-09"; } - - identity tunnel-type { - description "Type of tunneling technology"; - } - - typedef tunnel-type-ref { - description "Reference to a tunneling technology"; - type identityref { - base tunnel-type; - } - } - - identity tunnel-type-vxlan { - // FIXME: should be in a vxlan-specific model - description "VXLAN tunneling"; - base tunnel-type; - } - - augment "/nt:network-topology/nt:topology/nt:topology-types" { - ext:augment-identifier "topology-types-vbridge-augment"; - container vbridge-topology { - presence "Indicates a virtual bridge domain topology"; - } - } - - augment "/nt:network-topology/nt:topology" { - ext:augment-identifier "topology-vbridge-augment"; - when "./nt:topology-types/vbridge-topology"; - - // Pointer to the NETCONF topology which supports this bridge domain - // FIXME: must "../../nt:underlay-topology"; - - leaf tunnel-type { - description "Tunnel technology to use for encapsulation"; - type tunnel-type-ref; - } - - choice tunnel-parameters { - container vxlan { - // FIXME: should be in a vxlan-specific model - when "../type = tunnel-type-vxlan"; - leaf vni { - description "VNI to use for encap"; - type v3po:vxlan-vni; - mandatory true; - } - } - } - - uses v3po:bridge-domain-attributes; - } - - augment "/nt:network-topology/nt:topology/nt:node" { - ext:augment-identifier "node-vbridge-augment"; - when "../nt:topology-types/vbridge-topology"; - - - container bridge-member { - presence "Indicates this node is part of the bridge domain"; - - // Pointer to the NETCONF node which supports this bridge member - must "../../nt:supporting-node"; - - // FIXME: this is implementation specific, depends on whether - // the underlay has an a concept of a bridge domain. - leaf supporting-bridge-domain { - description - "Reference to the network element bridge domain, which has - been configured to support this virtual bridge domain on - this bridge member. - - This reference needs to be resolved against the supporting - node's configuration data store."; - config false; - type extref:external-reference; - } - } - } - - augment "/nt:network-topology/nt:topology/nt:node/nt:termination-point" { - ext:augment-identifier "termination-point-vbridge-augment"; - when "../bridge-member"; - - choice interface-type { - leaf user-interface { - description - "Reference to the network element interface, which is - configured to be a member of this virtual bridge domain. - - This reference needs to be resolved against the supporting - node's configuration data store."; - type extref:external-reference; - mandatory true; - } - leaf tunnel-interface { - description - "Reference to the network element interface, which is - configured to on the member to support exchange of packet - passing through this virtual bridge domain towards other - domain members. - - This reference needs to be resolved against the supporting - node's configuration data store."; - config false; - type extref:external-reference; - mandatory true; - } - } - } - - augment "/nt:network-topology/nt:topology/nt:link" { - when "../nt:topology-types/vbridge-topology"; - ext:augment-identifier "link-vbridge-augment"; - leaf tunnel { - description - "Reference to the network element tunnel interface supporting - cross-connect between two bridge members. - - This reference needs to be resolved against the supporting - node's operational data store."; - config false; - type extref:external-reference; - } - } -} |