3 namespace "urn:demo.simple-topology";
5 import simple-list-demo { prefix "simple"; revision-date 2008-01-01; }
6 import controller-network {prefix "cn";}
7 import mount {prefix "mnt";}
9 organization "OPEN DAYLIGHT";
10 contact "http://www.opendaylight.org/";
13 This module contains the definitions of elements that creates network
14 topology i.e. definition of network nodes and links. This module is
15 not designed to be used solely for network representation. This module
16 SHOULD be used as base module in defining the network topology.
19 revision "2013-02-08"{
20 reference " WILL BE DEFINED LATER";
27 deviation /base:system/base:user/base:type {
29 default "admin"; // new users are 'admin' by default
33 deviation /base:system/base:name-server {
39 deviation "/base:system" {
41 must "daytime or time";
54 description "Target IP address";
57 type inet:port-number;
58 description "Target port number";
62 augment "/cn:network/cn:topologies/cn:topology" {
71 leaf-list advertising-node-id {
78 mnt:mountpoint point {
79 mnt:target-ref target;
85 container destination {
101 must "ifType != 'ethernet' or " +
102 "(ifType = 'ethernet' and ifMTU = 1500)" {
103 error-message "An ethernet MTU must be 1500";
106 presence "test-presence";
109 This is the model of abstract topology which contains only Network
110 Nodes and Network Links. Each topology MUST be identified by
111 unique topology-id for reason that the store could contain many
118 It is presumed that datastore will contain many topologies. To
119 distinguish between topologies it is vital to have UNIQUE
124 container network-nodes {
127 description "The list of network nodes defined for topology.";
133 description "The Topology identifier of network-node.";
136 list network-interface {
143 leaf interface-address {
148 container node-attributes {
150 Additional attributes that can Network Node contains.
170 container network-links {
173 The Network Link which is defined by Local (Source) and
174 Remote (Destination) Network Nodes. Every link MUST be
175 defined either by identifier and his local and remote
176 Network Nodes (in real applications it is common that many
177 links are originated from one node and end up in same
178 remote node). To ensure that we would always know to
179 distinguish between links, every link SHOULD have
192 description "Source node identifier.";
196 container destination {
199 description "Destination node identifier.";
203 container link-attributes {
204 description "Aditional attributes that can Network Link contains.";
210 rpc activate-software-image {