1 module abstract-topology {
3 namespace "urn:model:abstract:topology";
6 import ietf-inet-types {
8 revision-date 2010-09-24;
11 organization "OPEN DAYLIGHT";
12 contact "http://www.opendaylight.org/";
15 "This module contains the definitions of elements that creates network
16 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.";
18 revision "2013-02-08" {
19 reference "~~~ WILL BE DEFINED LATER";
22 revision "2013-01-01" {
23 reference "~~~ WILL BE DEFINED LATER";
28 path "/tp:topology/tp:network-nodes/tp:network-node/tp:node-id";
30 description "This type is used for leafs that reference network node instance.";
35 path "/tp:topology/tp:network-links/tp:network-link/tp:link-id";
37 description "This type is used for leafs that reference network link instance.";
41 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.";
45 description "It is presumed that datastore will contain many topologies. To distinguish between topologies it is vital to have
46 UNIQUE topology identifier.";
49 container network-nodes {
55 description "The Topology identifier of network-node.";
58 container attributes {
59 description "Aditional attributes that can Network Node contains.";
61 description "The list of network nodes defined for topology.";
65 container network-links {
74 container source-node {
77 description "Source node identifier.";
81 container destination-node {
84 description "Destination node identifier.";
88 container attributes {
89 description "Aditional attributes that can Network Link contains.";
91 description "The Network Link which is defined by Local (Source) and Remote (Destination) Network Nodes. Every link MUST be defined either by identifier and
92 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.";