1 module abstract-topology {
3 namespace "urn:model:abstract:topology";
6 revision "2013-02-08" {
7 reference "http://www.opendaylight.org/";
12 path "/tp:topology/tp:network-nodes/tp:network-node/tp:node-id";
14 description "This type is used for leafs that reference network node instance.";
19 path "/tp:topology/tp:network-links/tp:network-link/tp:link-id";
21 description "This type is used for leafs that reference network link instance.";
25 description "This is the model of abstract topology which contains
26 only Network Nodes and Network Links. Each topology MUST be identified by unique
27 topology-id for reason that the store could contain many topologies.";
31 description "It is presumed that datastore will contain many topologies.
32 To distinguish between topologies it is vital to have
33 UNIQUE topology identifier.";
36 container network-nodes {
42 description "The Topology identifier of network-node.";
45 container attributes {
46 description "Aditional attributes that can Network Node contains.";
48 description "The list of network nodes defined for topology.";
52 container network-links {
61 container source-node {
64 description "Source node identifier.";
68 container destination-node {
71 description "Destination node identifier.";
75 container attributes {
76 description "Aditional attributes that can Network Link contains.";
78 description "The Network Link which is defined by Local (Source) and Remote (Destination)
79 Network Nodes. Every link MUST be defined either by identifier and
80 his local and remote Network Nodes (In real applications it is common that
81 many links are originated from one node and end up in same remote node).
82 To ensure that we would always know to distinguish between links, every link
83 SHOULD have identifier.";