We have a ton of trailing whitespace, clean it up.
Change-Id: Ib7f5ae567b83f5b5172386fc496728e8c48131c2
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
yang-version 1;
namespace "urn:opendaylight:controller:network:rpcs";
prefix "topos";
-
+
import ietf-inet-types { prefix "inet"; }
-
+
revision 2013-05-20 {
description "Initial demo";
}
-
+
rpc activate-software-image {
input {
leaf image-name {
}
}
}
-
+
rpc rock-the-house {
input {
leaf zip-code {
yang-version 1;
namespace "urn:opendaylight:controller:network";
prefix "topos";
-
+
import ietf-inet-types { prefix "inet"; }
-
+
revision 2013-05-20 {
description "Initial demo";
}
-
-
-
+
+
+
typedef topology-id {
type string;
}
description "This type is used for leafs that reference a link instance.";
// currently not used
}
-
+
typedef network-element-ref {
type leafref {
path "/network/network-elements/network-element/element-id";
typedef element-id {
type string;
}
-
+
container network {
container topologies {
list topology {
";
key "topology-id";
leaf topology-id {
- type topology-id;
+ type topology-id;
description "
It is presumed that datastore will contain many topologies. To
distinguish between topologies it is vital to have UNIQUE
container types {
description "
The container for definition of topology types.
- The augmenting modules should add empty optional leaf
+ The augmenting modules should add empty optional leaf
to this container to signalize topology type.
";
}
leaf supporting-ne {
type network-element-ref;
}
-
+
container termination-points {
list termination-point {
key "tp-id";
}
}
}
-
+
container links {
list link {
description "
identifier.
";
key "link-id";
-
+
leaf link-id {
type link-id;
}
- container source {
+ container source {
leaf source-node {
type node-ref;
description "Source node identifier.";
type tp-ref;
}
}
- container destination {
+ container destination {
leaf dest-node {
type node-ref;
description "Destination node identifier.";
}
}
}
-
+
rpc activate-software-image {
input {
leaf image-name {
}
}
}
-
+
rpc rock-the-house {
input {
leaf zip-code {
namespace "urn:opendaylight:controller:openflow";
prefix "of";
import controller-network {prefix cn;}
-
-
+
+
revision 2013-05-20 {
description "Initial demo";
}
-
+
type datapath-id;
}
}
-
+
augment "/cn:network/cn:network-elements/cn:network-element" {
leaf datapath-id {
type datapath-id;
container ports {
list port {
key "logical-port-id";
-
+
leaf logical-port-id {
type int32;
}
contact "http://www.opendaylight.org/";
description "
- This module contains the definitions of elements that creates network
+ This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is
not designed to be used solely for network representation. This module
SHOULD be used as base module in defining the network topology.
type string;
description "The Topology identifier of network-node.";
}
-
+
list network-interface {
key "interface-id";
-
+
leaf interface-id {
type uint8;
}
-
+
leaf interface-address {
type string;
}
}
-
+
container node-attributes {
description "
Additional attributes that can Network Node contains.
}
}
}
-
+
container network-links {
list network-link {
description "
namespace "urn:model:abstract:topology";
prefix "tp";
- import ietf-inet-types {
- prefix "inet";
+ import ietf-inet-types {
+ prefix "inet";
revision-date 2010-09-24;
}
contact "http://www.opendaylight.org/";
description
- "This module contains the definitions of elements that creates network
+ "This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is not designed to be used solely for network representation. This module SHOULD be used as base module in defining the network topology.";
revision "2013-02-08" {
reference "~~~ WILL BE DEFINED LATER";
}
-
+
revision "2013-01-01" {
reference "~~~ WILL BE DEFINED LATER";
}
-
+
typedef node-id-ref {
type leafref {
path "/tp:topology/tp:network-nodes/tp:network-node/tp:node-id";
description "The list of network nodes defined for topology.";
}
}
-
+
container network-links {
list network-link {
key "link-id";
revision "2013-02-08" {
reference "http://www.opendaylight.org/";
}
-
+
typedef node-id-ref {
type leafref {
path "/tp:topology/tp:network-nodes/tp:network-node/tp:node-id";
}
container topology {
- description "This is the model of abstract topology which contains
- only Network Nodes and Network Links. Each topology MUST be identified by unique
+ description "This is the model of abstract topology which contains
+ only Network Nodes and Network Links. Each topology MUST be identified by unique
topology-id for reason that the store could contain many topologies.";
leaf topology-id {
type string;
- description "It is presumed that datastore will contain many topologies.
+ description "It is presumed that datastore will contain many topologies.
To distinguish between topologies it is vital to have
UNIQUE topology identifier.";
}
description "The list of network nodes defined for topology.";
}
}
-
+
container network-links {
list network-link {
key "link-id";
container attributes {
description "Aditional attributes that can Network Link contains.";
}
- description "The Network Link which is defined by Local (Source) and Remote (Destination)
+ description "The Network Link which is defined by Local (Source) and Remote (Destination)
Network Nodes. Every link MUST be defined either by identifier and
- his local and remote Network Nodes (In real applications it is common that
- many links are originated from one node and end up in same remote node).
- To ensure that we would always know to distinguish between links, every link
+ his local and remote Network Nodes (In real applications it is common that
+ many links are originated from one node and end up in same remote node).
+ To ensure that we would always know to distinguish between links, every link
SHOULD have identifier.";
}
}
leaf tunnel-id {
type int32;
}
-
+
container foo {
leaf bar {
type string;
augment "/at:topology/at:network-links/at:network-link/at:attributes" {
leaf longitude {
- type decimal64 {
+ type decimal64 {
fraction-digits 2;
}
}
leaf latitude {
- type decimal64 {
+ type decimal64 {
fraction-digits 2;
}
}
typedef union-typedef2 {
type union {
- type string;
+ type string;
type int16;
}
- }
+ }
container parent-container {
leaf bit-leaf {
type uint8;
}
}
-
-// nested union in leaf
+
+// nested union in leaf
leaf lf {
type union {
type string;
type union {
type string;
type uint64;
- }
+ }
}
- }
- }
+ }
+ }
}
-
-// nested union in typedef
+
+// nested union in typedef
typedef type-union {
type union {
type string;
type union {
type uint32;
type int8;
- type string;
+ type string;
type union {
type string;
type uint64;
- }
+ }
}
- }
-
- }
+ }
+
+ }
}
\ No newline at end of file
* and is available at http://www.eclipse.org/legal/epl-v10.html
*/
module bit-and-union-in-leaf {
-
+
namespace "urn:bit:union:in:leaf";
prefix "sbd";
contact "http://www.opendaylight.org/";
revision 2013-06-26 {
-
+
}
-
+
typedef union-typedef {
type union {
type string {
type int16;
}
}
-
+
typedef union-typedef2 {
type union {
- type string;
+ type string;
type int16;
}
- }
-
+ }
+
container parent-container {
leaf bit-leaf {
type bits {
bit third-bit;
}
}
-
+
leaf union-leaf {
type union {
type int32;
type tls-fingerprint-type;
}
}
-
+
case sha224 {
leaf sha224 {
type tls-fingerprint-type;
}
}
-
+
case sha256 {
leaf sha256 {
type tls-fingerprint-type;
}
}
-
+
case sha384 {
leaf sha384 {
type tls-fingerprint-type;
}
- }
-
+ }
+
case sha512 {
leaf sha512 {
type tls-fingerprint-type;
yang-version 1;
namespace "urn:opendaylight:controller:network";
prefix "topos";
-
+
import ietf-inet-types { prefix "inet"; }
-
+
revision 2013-05-20 {
description "Initial demo";
}
-
-
-
+
+
+
typedef topology-id {
type string;
}
description "This type is used for leafs that reference a link instance.";
// currently not used
}
-
+
typedef network-element-ref {
type leafref {
path "/network/network-elements/network-element/element-id";
typedef element-id {
type string;
}
-
+
container network {
container topologies {
list topology {
";
key "topology-id";
leaf topology-id {
- type topology-id;
+ type topology-id;
description "
It is presumed that datastore will contain many topologies. To
distinguish between topologies it is vital to have UNIQUE
container types {
description "
The container for definition of topology types.
- The augmenting modules should add empty optional leaf
+ The augmenting modules should add empty optional leaf
to this container to signalize topology type.
";
}
leaf supporting-ne {
type network-element-ref;
}
-
+
container termination-points {
list termination-point {
key "tp-id";
}
}
}
-
+
container links {
list link {
description "
identifier.
";
key "link-id";
-
+
leaf link-id {
type link-id;
}
- container source {
+ container source {
leaf source-node {
type node-ref;
description "Source node identifier.";
type tp-ref;
}
}
- container destination {
+ container destination {
leaf dest-node {
type node-ref;
description "Destination node identifier.";
namespace "urn:opendaylight:controller:openflow";
prefix "of";
import controller-network {prefix cn;}
-
-
+
+
revision 2013-05-20 {
description "Initial demo";
}
-
+
type datapath-id;
}
}
-
+
augment "/cn:network/cn:network-elements/cn:network-element" {
leaf datapath-id {
type datapath-id;
container ports {
list port {
key "logical-port-id";
-
+
leaf logical-port-id {
type int32;
}
contact "http://www.opendaylight.org/";
description "
- This module contains the definitions of elements that creates network
+ This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is
not designed to be used solely for network representation. This module
SHOULD be used as base module in defining the network topology.
type string;
description "The Topology identifier of network-node.";
}
-
+
list network-interface {
key "interface-id";
-
+
leaf interface-id {
type uint8;
}
-
+
leaf interface-address {
type string;
}
}
-
+
container node-attributes {
description "
Additional attributes that can Network Node contains.
}
}
}
-
+
container network-links {
list network-link {
description "
contact "http://www.opendaylight.org/";
description
- "This module contains the definitions of elements that creates network
+ "This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is not designed to be used solely for network representation. This module SHOULD be used as base module in defining the network topology.";
revision "2013-02-08" {
reference "~~~ WILL BE DEFINED LATER";
}
-
+
revision "2013-01-01" {
reference "~~~ WILL BE DEFINED LATER";
}
-
+
typedef node-id-ref {
type leafref {
path "/tp:topology/tp:network-nodes/tp:network-node/tp:node-id";
}
}
}
-
+
container network-links {
list network-link {
key "link-id";
contact "http://www.opendaylight.org/";
description
- "This module contains the definitions of elements that creates network
+ "This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is not designed to be used solely for network representation. This module SHOULD be used as base module in defining the network topology.";
revision "2013-02-08" {
reference "~~~ WILL BE DEFINED LATER";
}
-
+
revision "2013-01-01" {
reference "~~~ WILL BE DEFINED LATER";
}
-
+
typedef node-id-ref {
type leafref {
path "/tp:topology/tp:network-nodes/tp:network-node/tp:node-id";
}
}
}
-
+
container network-links {
list network-link {
key "link-id";
contact "http://www.opendaylight.org/";
description "
- This module contains the definitions of elements that creates network
+ This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is
not designed to be used solely for network representation. This module
SHOULD be used as base module in defining the network topology.
leaf key1 {
type int8;
}
-
+
leaf key2 {
type string;
}
-
+
list inner-list {
key "key1";
-
+
leaf key1 {
type uint16;
}
-
+
leaf foo {
type int32;
}
}
-
+
leaf foo {
type int32;
}
}
-
+
list no-key-list {
leaf foo {
type int32;
}
-
+
leaf bar {
type decimal64 {
fraction-digits 2;
action something;
}
}
-
+
new-subnode-chc "some value from chc";
}
refine chc2 {
- mandatory "false";
- }
+ mandatory "false";
+ }
refine data {
mandatory "false";
must "something-else = 9";
module simple-bits-demo {
-
+
namespace "urn:simple:bits:demo";
prefix "sbd";
organization "OPEN DAYLIGHT";
- contact "http://www.opendaylight.org/";
+ contact "http://www.opendaylight.org/";
revision 2013-06-11 {
-
+
}
typedef byte-type {
}
bit forth-bit {
position 40;
- }
+ }
bit fifth-bit {
position 50;
- }
+ }
bit sixth-bit {
position 60;
- }
+ }
bit seventh-bit {
position 70;
- }
+ }
bit eight-bit {
position 80;
- }
+ }
}
}
type uint32;
}
-
+
container leaf-parent-container {
leaf byte-leaf {
type byte-type;
}
-
+
}
}
\ No newline at end of file
contact "http://www.opendaylight.org/";
description "
- This module contains the definitions of elements that creates network
+ This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is
not designed to be used solely for network representation. This module
SHOULD be used as base module in defining the network topology.
contact "http://www.opendaylight.org/";
description "
- This module contains the definitions of elements that creates network
+ This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is
not designed to be used solely for network representation. This module
SHOULD be used as base module in defining the network topology.
contact "http://www.opendaylight.org/";
description "
- This module contains the definitions of elements that creates network
+ This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is
not designed to be used solely for network representation. This module
SHOULD be used as base module in defining the network topology.
leaf list-key {
type int8;
}
-
+
container list-child-container {
leaf foo {
type uint8;
}
}
-
+
leaf foo {
type int32;
}
-
+
leaf-list simple-leaf-list {
type int32;
}
-
+
leaf bar {
type string;
config true;
- }
+ }
}
}
}
\ No newline at end of file
contact "http://www.opendaylight.org/";
revision 2013-06-18 {
-
+
}
module typedef_typedef {
-
+
namespace "urn:typedef:typedef";
prefix "sbd";
import ietf-inet-types {
prefix "inet";
revision-date 2010-09-24;
- }
+ }
organization "OPEN DAYLIGHT";
contact "http://www.opendaylight.org/";
revision 2013-07-09 {
-
+
}
position 20;
}
}
- }
-
-
+ }
+
+
typedef typedef-enum-fruit {
type enumeration {
enum "apple" {
value 2;
}
}
- }
-
+ }
+
typedef simple-typedef1 {
type uint8;
}
-
+
typedef simple-typedef2 {
type simple-typedef1;
}
-
+
typedef simple-typedef3 {
type simple-typedef2;
}
-
+
typedef simple-typedef4 {
type simple-typedef3;
}
-
+
typedef simple-typedef1-1 {
type uint16;
}
-
+
typedef union-typedef {
type union {
type simple-typedef1;
type typedef-enum-fruit;
}
}
-
+
typedef extended-typedef-union {
type union-typedef;
}
-
-
+
+
typedef extended-typedef-simple {
type simple-typedef1;
}
-
+
typedef extended-typedef-enum {
type typedef-enum-fruit;
}
namespace "urn:model:abstract:topology";
prefix "tp";
- import ietf-inet-types {
- prefix "inet";
+ import ietf-inet-types {
+ prefix "inet";
revision-date 2010-09-24;
}
contact "http://www.opendaylight.org/";
description
- "This module contains the definitions of elements that creates network
+ "This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is not designed to be used solely for network representation. This module SHOULD be used as base module in defining the network topology.";
revision "2013-02-08" {
reference "~~~ WILL BE DEFINED LATER";
}
-
+
revision "2013-01-01" {
reference "~~~ WILL BE DEFINED LATER";
}
description "The list of network nodes defined for topology.";
}
}
-
+
container network-links {
list network-link {
key "link-id";
}
-
+
grouping grouping-modul-test {
leaf leaf-grouping-modul-test {
type string;
grouping grouping-case-test {
leaf leaf-grouping-case-test1 {
type string;
- }
+ }
}
grouping grouping-choice-test {
}
}
}
-
+
grouping grouping-list-test {
leaf leaf-grouping-list-test {
type string;
leaf-list leaflist-grouping-list-test {
type string;
}
- }
+ }
grouping grouping-grouping-test {
leaf leaf-grouping-grouping {
type uint8;
}
}
-
+
grouping grouping-rpc-output-test {
leaf leaf-grouping-rpc-output-test {
type int8;
}
}
-
+
//grouping in GROUPING
grouping grouping-atest {
leaf leaf-grouping-test {
}
uses grouping-grouping-test;
}
-
-//grouping in MODUL
+
+//grouping in MODUL
// uses grouping-modul-test;
//grouping in RPC
output {
uses grouping-rpc-output-test;
}
- }
+ }
//grouping in CONTAINER
container container-test {
uses grouping-container-test;
}
-//grouping in CASE
+//grouping in CASE
container container-with-choicetest {
choice choice-test {
case a {
type string;
}
}
- case c {
- uses grouping-case-test;
+ case c {
+ uses grouping-case-test;
}
- }
- }
-
-//grouping in LIST
+ }
+ }
+
+//grouping in LIST
list list-test {
leaf list-leaf-test {
type string;
}
uses grouping-list-test;
- }
+ }
}
\ No newline at end of file
module grouping_uses_augment {
-
+
namespace "urn:grouping:uses:augment";
prefix "sbd";
type string;
}
}
-
+
container container-augment {
leaf leaf-container-augment1 {
leaf leaf-container-augment2 {
type int64;
}
- }
-
+ }
+
augment "/container-augment" {
- uses grouping-augment-test;
+ uses grouping-augment-test;
}
}
\ No newline at end of file
module grouping_uses_container {
-
+
namespace "urn:grouping:uses:container";
prefix "sbd";
revision 2013-07-18 {
}
-
+
grouping grouping-container-test {
leaf leaf-grouping-container-test1 {
type string;
type uint8;
}
}
-
+
//grouping in CONTAINER
container container-test {
leaf container-leaf-test {
module grouping_dependencies {
-
+
namespace "urn:grouping:dependencies";
prefix "sbd";
revision 2013-07-18 {
}
-
+
grouping grouping-U {
leaf leaf-grouping-U {
type string;
type string;
}
}
-
+
grouping grouping-Z {
leaf leaf-grouping-Z {
type string;
}
}
-
+
grouping grouping-ZZ {
leaf leaf-grouping-ZZ {
type string;
}
- }
+ }
}
\ No newline at end of file
module grouping_uses_grouping {
-
+
namespace "urn:grouping:uses:grouping";
prefix "sbd";
type string;
}
}
-
+
//grouping in GROUPING
grouping grouping-test {
}
uses grouping-grouping-test;
}
-
+
}
\ No newline at end of file
module grouping_uses_list {
-
+
namespace "urn:grouping:uses:list";
prefix "sbd";
type uint8;
}
}
-
-//grouping in MODUL
+
+//grouping in MODUL
uses grouping-modul-test;
}
\ No newline at end of file
module grouping_uses_notification {
-
+
namespace "urn:grouping:uses:notification";
prefix "sbd";
module grouping_uses_rpc {
-
+
namespace "urn:grouping:uses:rpc";
prefix "sbd";
revision 2013-07-18 {
}
-
+
grouping grouping-rpc-input-test {
container container-grouping-rpc-input-test {
type uint8;
}
}
-
+
grouping grouping-rpc-output-test {
leaf leaf-grouping-rpc-output-test {
type int8;
revision 2013-09-10 {
}
-
+
typedef tpdf {
type string;
}
-
+
container cont-outter {
container cont-inner {
- }
+ }
}
-
-
+
+
}
\ No newline at end of file
import ietf-inet-types { prefix "inet"; }
import abstract-prefixes { prefix "abs-pref"; }
-
+
organization "OPEN DAYLIGHT";
contact "http://www.opendaylight.org/";
description "
- This module contains the definitions of elements that creates network
+ This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is
not designed to be used solely for network representation. This module
SHOULD be used as base module in defining the network topology.
revision "2013-03-08" {
reference " WILL BE DEFINED LATER";
}
-
+
revision "2012-02-08" {
reference " WILL BE DEFINED LATER";
}
}
}
}
-
+
container network-links {
list network-link {
description "
yang-version 1;
namespace "urn:opendaylight.bar";
prefix "bar";
-
+
description "bar - Network topology is the arrangement of the various elements (links, nodes, etc.) of a computer network.[1][2] Essentially, it is the topological[3] structure of a network, and may be depicted physically or logically. Physical topology is the placement of the various components of a network, including device location and cable installation, while logical topology illustrates how data flows within a network, regardless of its physical design. Distances between nodes, physical interconnections, transmission rates, or signal types may differ between two networks, yet their topologies may be identical.";
reference "RFC 6020 - http://tools.ietf.org/html/rfc6020";
container network-topology {
description "network-topology - Network topology is the arrangement of the various elements (links, nodes, etc.) of a computer network.[1][2] Essentially, it is the topological[3] structure of a network, and may be depicted physically or logically. Physical topology is the placement of the various components of a network, including device location and cable installation, while logical topology illustrates how data flows within a network, regardless of its physical design. Distances between nodes, physical interconnections, transmission rates, or signal types may differ between two networks, yet their topologies may be identical.";
reference "RFC 6020 - http://tools.ietf.org/html/rfc6020";
-
+
list topology {
description "topology - Network topology is the arrangement of the various elements (links, nodes, etc.) of a computer network.[1][2] Essentially, it is the topological[3] structure of a network, and may be depicted physically or logically. Physical topology is the placement of the various components of a network, including device location and cable installation, while logical topology illustrates how data flows within a network, regardless of its physical design. Distances between nodes, physical interconnections, transmission rates, or signal types may differ between two networks, yet their topologies may be identical.";
reference "RFC 6020 - http://tools.ietf.org/html/rfc6020";
-
+
key "topology-id";
leaf topology-id {
description "topology-id - Network topology is the arrangement of the various elements (links, nodes, etc.) of a computer network.[1][2] Essentially, it is the topological[3] structure of a network, and may be depicted physically or logically. Physical topology is the placement of the various components of a network, including device location and cable installation, while logical topology illustrates how data flows within a network, regardless of its physical design. Distances between nodes, physical interconnections, transmission rates, or signal types may differ between two networks, yet their topologies may be identical.";
type int8;
}
}
-
+
leaf inclusion-rulez {
description "Specified rulez description.";
reference "RFC 6020 http://technet.com";
-
+
type string;
}
type enumeration {
enum include {
- description
- "This label will be included normally in the
+ description
+ "This label will be included normally in the
matching. This seems to be a little bit longer comment. I hear you very weel my darling.
Network topology is the arrangement of the various elements (links, nodes, etc.) of any other builder nodes types.";
}
enum exclude {
- description
- "This label will be excluded from the
+ description
+ "This label will be excluded from the
matching. This allows removing labels that
would have otherwise been included because of
inheritence rules.";
prefix "br";
revision-date 2013-10-08;
}
-
+
description "Baz - Network topology is the arrangement of the various elements (links, nodes, etc.) of a computer network.[1][2] Essentially, it is the topological[3] structure of a network, and may be depicted physically or logically. Physical topology is the placement of the various components of a network, including device location and cable installation, while logical topology illustrates how data flows within a network, regardless of its physical design. Distances between nodes, physical interconnections, transmission rates, or signal types may differ between two networks, yet their topologies may be identical.";
reference "RFC 6020 - http://tools.ietf.org/html/rfc6020";
leaf multi-topology-id {
description "Multi-topology-id - Network topology is the arrangement of the various elements (links, nodes, etc.) of a computer network.[1][2] Essentially, it is the topological[3] structure of a network, and may be depicted physically or logically. Physical topology is the placement of the various components of a network, including device location and cable installation, while logical topology illustrates how data flows within a network, regardless of its physical design. Distances between nodes, physical interconnections, transmission rates, or signal types may differ between two networks, yet their topologies may be identical.";
reference "RFC 6020 - http://tools.ietf.org/html/rfc6020";
-
+
type uint8 {
range "0..127";
}
prefix "br";
revision-date 2013-10-08;
}
-
+
description "Foo - Network topology is the arrangement of the various elements (links, nodes, etc.) of a computer network.[1][2] Essentially, it is the topological[3] structure of a network, and may be depicted physically or logically. Physical topology is the placement of the various components of a network, including device location and cable installation, while logical topology illustrates how data flows within a network, regardless of its physical design. Distances between nodes, physical interconnections, transmission rates, or signal types may differ between two networks, yet their topologies may be identical.";
reference "RFC 6020 - http://tools.ietf.org/html/rfc6020";
container igp-link-attributes {
description "Igp-link-attributes - Network topology is the arrangement of the various elements (links, nodes, etc.) of a computer network.[1][2] Essentially, it is the topological[3] structure of a network, and may be depicted physically or logically. Physical topology is the placement of the various components of a network, including device location and cable installation, while logical topology illustrates how data flows within a network, regardless of its physical design. Distances between nodes, physical interconnections, transmission rates, or signal types may differ between two networks, yet their topologies may be identical.";
reference "RFC 6020 - http://tools.ietf.org/html/rfc6020";
-
+
leaf name {
description "Name - Network topology is the arrangement of the various elements (links, nodes, etc.) of a computer network.[1][2] Essentially, it is the topological[3] structure of a network, and may be depicted physically or logically. Physical topology is the placement of the various components of a network, including device location and cable installation, while logical topology illustrates how data flows within a network, regardless of its physical design. Distances between nodes, physical interconnections, transmission rates, or signal types may differ between two networks, yet their topologies may be identical.";
reference "RFC 6020 - http://tools.ietf.org/html/rfc6020";
contact "http://www.opendaylight.org/";
description "
- This module contains the definitions of elements that creates network
+ This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is
not designed to be used solely for network representation. This module
SHOULD be used as base module in defining the network topology.
type string;
description "The Topology identifier of network-node.";
}
-
+
list network-interface {
key "interface-id";
-
+
leaf interface-id {
type uint8;
}
-
+
leaf interface-address {
type string;
}
}
-
+
container node-attributes {
description "
Additional attributes that can Network Node contains.
}
}
}
-
+
container network-links {
list network-link {
description "
contact "http://www.opendaylight.org/";
description "
- This module contains the definitions of elements that creates network
+ This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is
not designed to be used solely for network representation. This module
SHOULD be used as base module in defining the network topology.
leaf key1 {
type int8;
}
-
+
leaf key2 {
type string;
}
-
+
list inner-list {
key "key1";
-
+
leaf key1 {
type uint16;
}
-
+
leaf foo {
type int32;
}
}
-
+
leaf foo {
type int32;
}
}
-
+
list no-key-list {
leaf foo {
type int32;
}
-
+
leaf bar {
type decimal64 {
fraction-digits 2;
contact "http://www.opendaylight.org/";
description "
- This module contains the definitions of elements that creates network
+ This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is
not designed to be used solely for network representation. This module
SHOULD be used as base module in defining the network topology.
contact "http://www.opendaylight.org/";
description "
- This module contains the definitions of elements that creates network
+ This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is
not designed to be used solely for network representation. This module
SHOULD be used as base module in defining the network topology.
contact "http://www.opendaylight.org/";
description "
- This module contains the definitions of elements that creates network
+ This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is
not designed to be used solely for network representation. This module
SHOULD be used as base module in defining the network topology.
leaf list-key {
type int8;
}
-
+
container list-child-container {
leaf foo {
type uint8;
}
}
-
+
leaf foo {
type int32;
}
-
+
leaf-list simple-leaf-list {
type int32;
}
-
+
leaf bar {
type string;
config true;
- }
+ }
}
}
}
contact "WILL-BE-DEFINED-LATER";
description
- "This module contains the definitions of elements that creates network
+ "This module contains the definitions of elements that creates network
topology i.e. definition of network nodes and links. This module is not designed to be used solely for network representation. This module SHOULD be used as base module in defining the network topology.";
revision "2013-02-08" {
reference "~~~ WILL BE DEFINED LATER";
}
-
+
revision "2013-01-01" {
reference "~~~ WILL BE DEFINED LATER";
}
-
+
typedef node-id-ref {
type leafref {
path "/tp:topology/tp:network-nodes/tp:network-node/tp:node-id";
}
}
}
-
+
container network-links {
list network-link {
key "link-id";
}
}
}
-
+
identity crypto-base {
description "crypto-base description";
}
-
+
identity crypto-alg {
base crypto-base;
description "crypto-alg description";
}
-
+
grouping target {
container nodes {
leaf source {
type string;
}
}
-
+
leaf idreftest {
type identityref {
base crypto-alg;
}
}
-
+
}
type ipv6-address-binary;
}
}
-
+
container root {
leaf ip-address {
type ip-address-binary;
import yang-ext { prefix ext; }
description
- "Test model for testing of registering rpc service on binding independent mount point
+ "Test model for testing of registering rpc service on binding independent mount point
and retrieving rpc service via binding aware mount point.";
revision "2014-07-01" {
identity test-context {
description "Test Context";
}
-
+
typedef encapsulated-route {
type instance-identifier;
}
-
+
grouping route-in-grouping {
leaf route {
type instance-identifier;
ext:context-reference test-context;
}
}
-
+
grouping encapsulated-route-in-grouping {
leaf route {
type encapsulated-route;
prefix "rpc";
description
- "Test model for testing of registering rpc service on binding independent mount point
+ "Test model for testing of registering rpc service on binding independent mount point
and retrieving rpc service via binding aware mount point.";
revision "2014-07-01" {
yang-version 1;
namespace "urn:opendaylight:params:xml:ns:yang:controller:md:sal:dom:store:test";
prefix "store-test";
-
+
revision "2014-03-13" {
description "Initial revision.";
}
prefix "odl-general-entity";
description "Defines a model to describe a general entity whose path can be used as an ID for an entity that isn't otherwise modelled";
-
+
revision 2015-09-30 {
description "Initial revision";
}
module opendaylight-l2-types {
- namespace "urn:opendaylight:l2:types";
- prefix "ethertype";
-
- description
- "Copyright (c) 2013 Cisco Systems, Inc. and others. All rights reserved.
-
- This program and the accompanying materials are made available under the
- terms of the Eclipse Public License v1.0 which accompanies this distribution,
- and is available at http://www.eclipse.org/legal/epl-v10.html";
-
- revision "2013-08-27" {
- description "Initial revision";
- }
-
- typedef vlan-pcp {
- description
- "IEEE 802.1p priority. It indicates the frame priority level.
- Values are from 0 (best effort) to 7 (highest);
- 1 represents the lowest priority.";
- type uint8 {
- range "0..7";
- }
- }
-
- typedef vlan-dei {
- description
- "Drop Eligible Indicator (DEI): a 1-bit field. (formerly CFI).
- May be used separately or in conjunction with PCP to indicate frames
- eligible to be dropped in the presence of congestion.";
- type boolean;
- }
-
- typedef vlan-id {
- type uint16 {
- range "0..4095";
- }
- }
-
-
- typedef ether-type {
- type uint32;
- }
+ namespace "urn:opendaylight:l2:types";
+ prefix "ethertype";
+
+ description
+ "Copyright (c) 2013 Cisco Systems, Inc. and others. All rights reserved.
+
+ This program and the accompanying materials are made available under the
+ terms of the Eclipse Public License v1.0 which accompanies this distribution,
+ and is available at http://www.eclipse.org/legal/epl-v10.html";
+
+ revision "2013-08-27" {
+ description "Initial revision";
+ }
+
+ typedef vlan-pcp {
+ description
+ "IEEE 802.1p priority. It indicates the frame priority level.
+ Values are from 0 (best effort) to 7 (highest);
+ 1 represents the lowest priority.";
+ type uint8 {
+ range "0..7";
+ }
+ }
+
+ typedef vlan-dei {
+ description
+ "Drop Eligible Indicator (DEI): a 1-bit field. (formerly CFI).
+ May be used separately or in conjunction with PCP to indicate frames
+ eligible to be dropped in the presence of congestion.";
+ type boolean;
+ }
+
+ typedef vlan-id {
+ type uint16 {
+ range "0..4095";
+ }
+ }
+
+ typedef ether-type {
+ type uint32;
+ }
}
Code Review / mdsal.git / commitdiff