Opendaylight-boron Study notes: 2 Dlux module

environment and software release notes

===

Sn-controller:

Cpu:2 cores

Ram:4gb

Disk:32gb

Operating system:centos7 x86_64 1611 (Linux 3.10.0-514) Infrastructure Server

IP1:10.0.3.100/24 (Public Network)

IP2:172.16.3.100/24 (SDN Network)

===

Opendaylight:boron

Download Address Reference

Using the Opendaylight User Interface (dlux) installation Dlux

Log in to the bin in the Opendaylight installation directory and open the Karaf console:

[Root@sn-controller bin]#./karaf
opendaylight-user@root>feature:install Odl-dlux-all
Opendaylight-user@root>logout

The Odl-dlux-all contains the following components:
* Odl-dlux-core
* Odl-dlux-node
* Odl-dlux-yangui
* Odl-dlux-yangvisualizer

* Remark: *

Under
Opendaylight Dlux introduce and solve the problem that the Web interface cannot display nodes
Instructions, you need to perform the following patches to resolve the problem that the Web cannot display nodes: Download restangular.min.js according to the link. Into the SYSTEM/ORG/OPENDAYLIGHT/DLUX/LOADER.IMPLEMENTATION/0.4.1-BORON-SR1 directory under the extracted Opendaylight-boron, You will see the Loader.implementation-0.4.1-boron-sr1.jar file, use the compression tool to open it and see the Dlux folder, and go to vendor/restangular/under that folder. The dist file clip will see the restangular.min.js file and delete it. and add the downloaded restangular.min.js. Delete the Data folder under Opendaylight-boron. Functional Experience Login

Use the browser to enter the address http://10.0.3.100:8181/index.html can open the ODL control page, the user name and password default to admin. combined with mininet using Opendaylight

Due to the limitations of the experimental environment, the creation of a network topology using a virtual machine with Mininet installed allows us to enable opendaylight to perform functional testing in a simulated network environment.

mininet Virtual machine parameters: HOSTNAME:MININET-VM1 Cpu:2 Nuclear RAM:4GB ip1:10.0.3.101 (Public network) ip2:172.16.3.101 (SDN Network)

Use Mininet to create a simple topology and connect to the Opendaylight:

mininet@mininet-vm1:~$ sudo mn--controller=remote,ip=10.0.3.100,port=6633
mininet> Pingall

A simple network topology can be seen in the Topology tab of the ODL control page: A OvS switch and two hosts. And in the Nodes page, you can see the OvS connection information, flow table and so on. Yang UI

In the ODL control page, with the Yang UI tag, the Yang UI allows the user to interact with yang-based Md-sal datastore through the ODL control page. When you click on the tab, you'll see a list of APIs.

Select the following API list in order: Network-topology = = > Operational = = > network-topology

Click the Send button and there will be information about the current network topology at the bottom of the page. Then click the Display Topology button to display the currently acquired network topology as a graphical representation. The network topology is consistent with the network topology seen in the topology tag.

Using the developer tool to make an HTTP request grab, you will find that when you press the Send button, a request is sent:

Request Url:http://10.0.3.100:8181/restconf/operational/network-topology:network-topology
Request Method:GET
Status code:200 OK
Remote address:10.0.3.100:8181
Referrer policy:no-referrer-when-downgrade

Accept:application/json, text/ Plain, */*
accept-encoding:gzip, deflate, sdch
accept-language:en-us,en;q=0.8
authorization:basic ywrtaw46ywrtaw4=
connection:keep-alive
cookie:jsessionid=1mx6quzomhkm057698iwg9r3a
Host : 10.0.3.100:8181
referer:http://10.0.3.100:8181/index.html
user-agent:mozilla/5.0 (X11; Linux x86_64) applewebkit/537.36 (khtml, like Gecko) chrome/58.0.3029.110 safari/537.36

You will then receive the following response:

Content-encoding:gzip Content-type:application/json Server:jetty (8.1.19.v20160209) Transfer-Encoding:chunked Vary: Accept-encoding, user-agent {"network-topology": {"Topology": [{"Topology-id": "Flow:1", "node": [{"Node-id": "Host:c2 : E3:9e:9d:ba:d1 "," Termination-point ": [{" Tp-id ":" Host:c2:e3:9e:9d:ba:d1 "}]," Host-tracker-service: Attachment-points ": [{" Tp-id ":" Openflow:1:1 "," CORRESPONDING-TP ":" Host:c2:e3:9e:9d:ba:d1 "," Active ": true}]," Host-tracker-service:id ":" C2:e3:9e:9d:ba:d1 "," host-tracker-service:addresses ": [{" id ": 6," Mac ":" C2:e3:9e:9d:ba: D1 "," First-seen ": 1494558215486," Last-seen ": 1494558215486," IP ":" 10.0.0.1 "}]},{" Node-id ":" Openflow:1 "," Termination-point ": [{" Tp-id ":" Openflow:1:1 "," Opendaylight-topology-inventory:inventory-node-connector-ref ":"/ Opendaylight-inventory:nodes/opendaylight-inventory:node[opendaylight-inventory:id= ' Openflow:1 ']/ Opendaylight-inventory:node-connector[opendaylight-inventory:id= ' openflow:1:1 '] "},{" Tp-id ":" Openflow:1:2 "," Opendaylight-topology-inventory:inventory-node-coNnector-ref ":"/opendaylight-inventory:nodes/opendaylight-inventory:node[opendaylight-inventory:id= ' openflow:1 ' ]/opendaylight-inventory:node-connector[opendaylight-inventory:id= ' Openflow:1:2 '] "},{" Tp-id ":" Openflow:1:LOCAL "," Opendaylight-topology-inventory:inventory-node-connector-ref ":"/opendaylight-inventory:nodes/ Opendaylight-inventory:node[opendaylight-inventory:id= ' Openflow:1 ']/opendaylight-inventory:node-connector[ Opendaylight-inventory:id= ' openflow:1:local '] "}", "Opendaylight-topology-inventory:inventory-node-ref": "/ Opendaylight-inventory:nodes/opendaylight-inventory:node[opendaylight-inventory:id= ' openflow:1 '] "},{" Node-id ": "host:32:1e:69:45:3b:4e", "Termination-point": [{"Tp-id": "host:32:1e:69:45:3b:4e"}], "Host-tracker-service: Attachment-points ": [{" Tp-id ":" Openflow:1:2 "," CORRESPONDING-TP ":" host:32:1e:69:45:3b:4e "," Active ": true}]," Host-tracker-service:id ":" 32:1e:69:45:3b:4e "," host-tracker-service:addresses ": [{" id ": 7," Mac ":" 32:1e:69:45:3b : 4e "," First-seen ": 1494558216492," Last-seen ": 1494558216492, "IP": "10.0.0.2"}]}], "link": [{"Link-id": "openflow:1:2/host:32:1e:69:45:3b:4e", "source": {"Source-node ":" Openflow:1 "," SOURCE-TP ":" Openflow:1:2 "}," destination ": {" DEST-TP ":" host:32:1e:69:45:3b:4e "," Dest-node ":" Host : 32:1e:69:45:3b:4e "}},{" Link-id ":" Host:32:1e:69:45:3b:4e/openflow:1:2 "," source ": {" Source-node ":" host:32:1e : 69:45:3b:4e "," SOURCE-TP ":" host:32:1e:69:45:3b:4e "}," destination ": {" DEST-TP ":" Openflow:1:2 "," Dest-node ":" Openflow:1 "}},{" Link-id ":" Host:c2:e3:9e:9d:ba:d1/openflow:1:1 "," source ": {" Source-node ":" Host:c2:e3:9e:9d:ba:d1 "," SOURCE-TP ":" Host:c2:e3:9e:9d:ba:d1 "}," destination ": {" DEST-TP ":" Openflow:1:1 "," Dest-node ":" Openflow:1 "}},{" Link-id ":" Openflow:1:1/host:c2:e3:9e:9d:ba:d1 "," source ": {" Source-node ":" Openflow:1 "," SOURCE-TP ":" Openflow:1:1 " }, "destination": {"DEST-TP": "Host:c2:e3:9e:9d:ba:d1", "Dest-node": "Host:c2:e3:9e:9d:ba:d1"}}]},{"Topology-id": " Netvirt:1 "},{" Topology-id ":" Ovsdb:1 "},{" Topology-id ":" Hwvtep:1 "}]}}

The

can be found in the response is the current network topology information, including node information, link information and so on.