-module abstract-topology {\r
- yang-version 1;\r
- namespace "urn:model:abstract:topology";\r
- prefix "tp";\r
-\r
- import ietf-inet-types { \r
- prefix "inet"; \r
- revision-date 2010-09-24;\r
- }\r
-\r
- organization "Cisco";\r
- contact "WILL-BE-DEFINED-LATER";\r
-\r
- description\r
- "This module contains the definitions of elements that creates network \r
- 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.";\r
-\r
- revision "2013-02-08" {\r
- reference "~~~ WILL BE DEFINED LATER";\r
- }\r
- \r
- revision "2013-01-01" {\r
- reference "~~~ WILL BE DEFINED LATER";\r
- }\r
- \r
- typedef node-id-ref {\r
- type leafref {\r
- path "/tp:topology/tp:network-nodes/tp:network-node/tp:node-id";\r
- }\r
- description "This type is used for leafs that reference network node instance.";\r
- }\r
-\r
- typedef link-id-ref {\r
- type leafref {\r
- path "/tp:topology/tp:network-links/tp:network-link/tp:link-id";\r
- }\r
- description "This type is used for leafs that reference network link instance.";\r
- }\r
-\r
- container topology {\r
- 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.";\r
-\r
- leaf topology-id {\r
- type inet:uri;\r
- description "It is presumed that datastore will contain many topologies. To distinguish between topologies it is vital to have\r
- UNIQUE topology identifier.";\r
- }\r
-\r
- container network-nodes {\r
- list network-node {\r
- key "node-id";\r
-\r
- leaf node-id {\r
- type inet:uri;\r
- description "The Topology identifier of network-node.";\r
- }\r
-\r
- container attributes {\r
- description "Aditional attributes that can Network Node contains.";\r
- }\r
- description "The list of network nodes defined for topology.";\r
- }\r
- }\r
- \r
- container network-links {\r
- list network-link {\r
- key "link-id";\r
-\r
- leaf link-id {\r
- type inet:uri;\r
- description "";\r
- }\r
-\r
- container source-node {\r
- leaf id {\r
- type node-id-ref;\r
- description "Source node identifier.";\r
- }\r
- }\r
-\r
- container destination-node {\r
- leaf id {\r
- type node-id-ref;\r
- description "Destination node identifier.";\r
- }\r
- }\r
-\r
- container attributes {\r
- description "Aditional attributes that can Network Link contains.";\r
- }\r
- description "The Network Link which is defined by Local (Source) and Remote (Destination) Network Nodes. Every link MUST be defined either by identifier and\r
- 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.";\r
- }\r
- }\r
- }\r
+module abstract-topology {
+ yang-version 1;
+ namespace "urn:model:abstract:topology";
+ prefix "tp";
+
+ import ietf-inet-types {
+ prefix "inet";
+ revision-date 2010-09-24;
+ }
+
+ organization "OPEN DAYLIGHT";
+ contact "http://www.opendaylight.org/";
+
+ description
+ "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 "This type is used for leafs that reference network node instance.";
+ }
+
+ typedef link-id-ref {
+ type leafref {
+ path "/tp:topology/tp:network-links/tp:network-link/tp:link-id";
+ }
+ description "This type is used for leafs that reference network link instance.";
+ }
+
+ 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 topology-id for reason that the store could contain many topologies.";
+
+ leaf topology-id {
+ type inet:uri;
+ description "It is presumed that datastore will contain many topologies. To distinguish between topologies it is vital to have
+ UNIQUE topology identifier.";
+ }
+
+ container network-nodes {
+ list network-node {
+ key "node-id";
+
+ leaf node-id {
+ type inet:uri;
+ description "The Topology identifier of network-node.";
+ }
+
+ container attributes {
+ description "Aditional attributes that can Network Node contains.";
+ }
+ description "The list of network nodes defined for topology.";
+ }
+ }
+
+ container network-links {
+ list network-link {
+ key "link-id";
+
+ leaf link-id {
+ type inet:uri;
+ description "";
+ }
+
+ container source-node {
+ leaf id {
+ type node-id-ref;
+ description "Source node identifier.";
+ }
+ }
+
+ container destination-node {
+ leaf id {
+ type node-id-ref;
+ description "Destination node identifier.";
+ }
+ }
+
+ container attributes {
+ description "Aditional attributes that can Network Link contains.";
+ }
+ 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 SHOULD have identifier.";
+ }
+ }
+ }
}
\ No newline at end of file
Code Review / controller.git / blobdiff