2 * Copyright (c) 2014 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 module controller-network {
10 namespace "urn:opendaylight:controller:network";
13 import ietf-inet-types { prefix "inet"; }
16 description "Initial demo";
36 description "identifier for termination points on a port";
41 path "/network/topologies/topology/nodes/node/termination-points/termination-point/tp-id";
44 typedef topology-ref {
46 path "/network/topologies/topology/topology-id";
48 description "This type is used for leafs that reference topology identifier instance.";
54 path "/network/topologies/topology/nodes/node/node-id";
56 description "This type is used for leafs that reference a node instance.";
61 path "/network/topologies/topology/links/link/link-id";
63 description "This type is used for leafs that reference a link instance.";
67 typedef network-element-ref {
69 path "/network/network-elements/network-element/element-id";
79 container topologies {
82 This is the model of abstract topology which contains only Network
83 Nodes and Network Links. Each topology MUST be identified by
84 unique topology-id for reason that the store could contain many
91 It is presumed that datastore will contain many topologies. To
92 distinguish between topologies it is vital to have UNIQUE
99 The container for definition of topology types.
100 The augmenting modules should add empty optional leaf
101 to this container to signalize topology type.
107 description "The list of network nodes defined for topology.";
112 description "The Topology identifier of network-node.";
116 type network-element-ref;
119 container termination-points {
120 list termination-point {
133 The Network Link which is defined by Local (Source) and
134 Remote (Destination) Network Nodes. Every link MUST be
135 defined either by identifier and his local and remote
136 Network Nodes (in real applications it is common that many
137 links are originated from one node and end up in same
138 remote node). To ensure that we would always know to
139 distinguish between links, every link SHOULD have
150 description "Source node identifier.";
156 container destination {
159 description "Destination node identifier.";
169 container network-elements {
171 list network-element {