2 * Copyright (c) 2013 Cisco Systems, Inc. and others. All rights reserved.
4 * This program and the accompanying materials are made available under the
5 * terms of the Eclipse Public License v1.0 which accompanies this distribution,
6 * and is available at http://www.eclipse.org/legal/epl-v10.html
8 // vi: set smarttab sw=4 tabstop=4:
9 module abstract-topology {
14 import ietf-inet-types { prefix "inet"; }
15 import abstract-prefixes { prefix "abs-pref"; }
17 organization "OPEN DAYLIGHT";
18 contact "http://www.opendaylight.org/";
21 This module contains the definitions of elements that creates network
22 topology i.e. definition of network nodes and links. This module is
23 not designed to be used solely for network representation. This module
24 SHOULD be used as base module in defining the network topology.
27 revision "2013-02-08" {
28 reference " WILL BE DEFINED LATER";
31 revision "2013-03-08" {
32 reference " WILL BE DEFINED LATER";
35 revision "2012-02-08" {
36 reference " WILL BE DEFINED LATER";
39 typedef topology-id-ref {
41 path "/tp:topology/tp:topology-id";
43 description "This type is used for leafs that reference topology identifier instance.";
46 typedef network-node-id-ref {
48 path "/tp:topology/tp:network-nodes/tp:network-node/tp:node-id";
50 description "This type is used for leafs that reference network node instance.";
55 path "/tp:topology/tp:network-links/tp:network-link/tp:link-id";
57 description "This type is used for leafs that reference network link instance.";
62 This is the model of abstract topology which contains only Network
63 Nodes and Network Links. Each topology MUST be identified by
64 unique topology-id for reason that the store could contain many
71 It is presumed that datastore will contain many topologies. To
72 distinguish between topologies it is vital to have UNIQUE
77 container network-nodes {
79 description "The list of network nodes defined for topology.";
85 description "The Topology identifier of network-node.";
88 container attributes {
90 Additional attributes that can Network Node contains.
96 container network-links {
99 The Network Link which is defined by Local (Source) and
100 Remote (Destination) Network Nodes. Every link MUST be
101 defined either by identifier and his local and remote
102 Network Nodes (in real applications it is common that many
103 links are originated from one node and end up in same
104 remote node). To ensure that we would always know to
105 distinguish between links, every link SHOULD have
118 description "Source node identifier.";
122 container destination {
125 description "Destination node identifier.";
129 container attributes {
130 description "Aditional attributes that can Network Link contains.";
136 //TODO: add base operations