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";}
11 contact "WILL-BE-DEFINED-LATER";
14 This module contains the definitions of elements that creates network
15 topology i.e. definition of network nodes and links. This module is
16 not designed to be used solely for network representation. This module
17 SHOULD be used as base module in defining the network topology.
20 revision "2013-02-08"{
21 reference " WILL BE DEFINED LATER";
28 deviation /base:system/base:user/base:type {
30 default "admin"; // new users are 'admin' by default
34 deviation /base:system/base:name-server {
40 deviation "/base:system" {
42 must "daytime or time";
55 description "Target IP address";
58 type inet:port-number;
59 description "Target port number";
63 augment "/cn:network/cn:topologies/cn:topology" {
72 leaf-list advertising-node-id {
79 mnt:mountpoint point {
80 mnt:target-ref target;
86 container destination {
102 must "ifType != 'ethernet' or " +
103 "(ifType = 'ethernet' and ifMTU = 1500)" {
104 error-message "An ethernet MTU must be 1500";
107 presence "test-presence";
110 This is the model of abstract topology which contains only Network
111 Nodes and Network Links. Each topology MUST be identified by
112 unique topology-id for reason that the store could contain many
119 It is presumed that datastore will contain many topologies. To
120 distinguish between topologies it is vital to have UNIQUE
125 container network-nodes {
128 description "The list of network nodes defined for topology.";
134 description "The Topology identifier of network-node.";
137 list network-interface {
144 leaf interface-address {
149 container node-attributes {
151 Additional attributes that can Network Node contains.
171 container network-links {
174 The Network Link which is defined by Local (Source) and
175 Remote (Destination) Network Nodes. Every link MUST be
176 defined either by identifier and his local and remote
177 Network Nodes (in real applications it is common that many
178 links are originated from one node and end up in same
179 remote node). To ensure that we would always know to
180 distinguish between links, every link SHOULD have
193 description "Source node identifier.";
197 container destination {
200 description "Destination node identifier.";
204 container link-attributes {
205 description "Aditional attributes that can Network Link contains.";
211 rpc activate-software-image {