3 ODL-SDNi Developer Guide
4 ========================
9 This project aims at enabling inter-SDN controller communication by
10 developing SDNi (Software Defined Networking interface) as an
11 application (ODL-SDNi App).
16 - SDNi Aggregator: Northbound SDNi plugin acts as an aggregator for
17 collecting network information such as topology, stats, host etc.
18 This plugin can be evolving as per needs of network data requested to
19 be shared across federated SDN controllers.
21 - SDNi API: API view autogenerated and accessible through RESTCONF to
22 fetch the aggregated information from the northbound plugin – SDNi
23 aggregator.The RESTCONF protocol operates on a conceptual datastore
24 defined with the YANG data modeling language.
26 - SDNi Wrapper: SDNi BGP Wrapper will be responsible for the sharing
27 and collecting information to/from federated controllers.
29 - SDNi UI:This component displays the SDN controllers connected to each
35 - SDNiAggregator connects with the Base Network Service Functions of
36 the controller. Currently it is querying network topology through
37 MD-SAL for creating SDNi network capability.
39 - SDNiAggregator is customized to retrieve the host controller’s
40 details, while running the controller in cluster mode. Rest of the
41 northbound APIs of controller will retrieve the entire topology
42 information of all the connected controllers.
44 - The SDNiAggregator creates a topology structure.This structure is
45 populated by the various network funtions.
50 Topology and QoS data is fetched from SDNiAggregator through RESTCONF.
52 `http://${controlleripaddress}:8181/apidoc/explorer/index.html <http://${controlleripaddress}:8181/apidoc/explorer/index.html>`__
54 `http://${ipaddress}:8181/restconf/operations/opendaylight-sdni-topology-msg:getAllPeerTopology <http://${ipaddress}:8181/restconf/operations/opendaylight-sdni-topology-msg:getAllPeerTopology>`__
56 **Peer Topology Data:** Controller IP Address, Links, Nodes, Link
57 Bandwidths, MAC Address of switches, Latency, Host IP address.
59 `http://${ipaddress}:8181/restconf/operations/opendaylight-sdni-qos-msg:get-all-node-connectors-statistics <http://${ipaddress}:8181/restconf/operations/opendaylight-sdni-qos-msg:get-all-node-connectors-statistics>`__
61 **QOS Data:** Node, Port, Transmit Packets, Receive Packets, Collision
62 Count, Receive Frame Error, Receive Over Run Error, Receive Crc Error
64 `http://${ipaddress}:8181/restconf/operations/opendaylight-sdni-qos-msg:get-all-peer-node-connectors-statistics <http://${ipaddress}:8181/restconf/operations/opendaylight-sdni-qos-msg:get-all-peer-node-connectors-statistics>`__
66 **Peer QOS Data:** Node, Port, Transmit Packets, Receive Packets,
67 Collision Count, Receive Frame Error, Receive Over Run Error, Receive
73 .. figure:: ./images/SDNiWrapper.png
78 - SDNiWrapper is an extension of ODL-BGPCEP where SDNi topology data is
79 exchange along with the Update NLRI message. Refer
80 http://tools.ietf.org/html/draft-ietf-idr-ls-distribution-04 for more
83 - SDNiWrapper gets the controller’s network capabilities through SDNi
84 Aggregator and serialize it in Update NLRI message. This NLRI message
85 will get exchange between the clustered controllers through
86 BGP-UPDATE message. Similarly peer controller’s UPDATE message is
87 received and unpacked then format to SDNi Network capability data,
88 which will be stored for further purpose.
93 This component displays the SDN controllers connected to each other.
95 http://localhost:8181/index.html#/sdniUI/sdnController
97 API Reference Documentation
98 ---------------------------
101 `http://${controlleripaddress}:8181/apidoc/explorer/index.html <http://${controlleripaddress}:8181/apidoc/explorer/index.html>`__,
102 sign in, and expand the opendaylight-sdni panel. From there, users can
103 execute various API calls to test their SDNi deployment.