- 22 Oct, 2015 7 commits
-
-
Device VLAN is set through configuration, subscriber VLAN can be added using CLI (eventually this will come through a call from the AAA app). Moving towards generalizing this app as an 'Access Device' app rather than purely OLT. Change-Id: I9b82b39f6a2dee2c6f10f3fd13b261f3e0313db7
Jonathan Hart authored -
Some kind of List (e.g. ArrayList) allow the existence of null element Add protection here in case someone call sw.sendMsg(List<OFMessage>) and pass a list with null element Change-Id: Ida2ffbb196d2fdcb23b911365fa3c1231eab92ed
Charles Chan authored
- 21 Oct, 2015 8 commits
-
-
- AnnotateDeviceCommand takes device ID only on 1st parameter Change-Id: Ib51efad6559a2faa5cbf7955698dc45e9b5a43c3
HIGUCHI Yuta authored -
PIM Address families IPv4 and IPv6 Change-Id: I8ae675fa1df052c4ef0b73b27449add534cc5c3c
Rusty Eddy authored -
Action "Set-Queue" (OFPAT_SET_QUEUE) is not yet implemented. This patch adds such a QUEUE Treatment and implements it using the Set-Queue action of OpenFlow 1.3. The --setQueue parameter can be used when defining intents so that flows with the respective Set-Queue action are installed. This includes contributions by Michael Jarschel and Arne Schwabe and is the result of our ONOS Hackaton project at EWSDN 2015. Change-Id: Ie7bf01e8fd90fe68977477327ac4f53d7930e186
Steffen Gebert authored -
There is a time gap between controller is elected as the master of a switch and controller actually becomes the master of a switch (receives ROLE_REPLY). During this time gap, OF messages destined for the switch will be sent to this controller. However, the OF message can only be sent to the switch after controller receives the ROLE_REPLY. Change-Id: I32d68384226e272658a0c9de2d32ae9e1cc39b6a
Charles Chan authored
- 20 Oct, 2015 7 commits
-
-
- updated TopoJson to include device badge in JSON output. Change-Id: I7fc0ec226c378a0395cd1eec765cb7bc867f9100
Simon Hunt authored -
related to CORD-200, CORD-209 - fix typo in network-cfg.json - remove segmentrouting_dell.conf since we don't need this anymore with the new Network Configuration Subsystem Change-Id: I5dcb2e2e0e6b89c4770df2485a8d27fbcc05cf67
Charles Chan authored -
- Handled situations where ovsdb, integration bridge, or vxlan port are already connected or exists when the application activated - Don't make use of mastership for ovsdb device, it does not work well in device disconnected or re-connected situations Change-Id: I002948f4a06126430f6019c79a0d84df16c9399c
Hyunsun Moon authored
-
- 19 Oct, 2015 7 commits
-
-
No longer needed because RADIUS packets come directly from UDP and not as packet in. Change-Id: I91fc37fc973c25a4b42c928ce6de41e71331f59d
Ray Milkey authored
- 17 Oct, 2015 3 commits
-
-
length parameters to deserialize the correct area of data buffer. Change-Id: I5d8869c25d397d5d07aad014ef00d0decef22d4f
Rusty Eddy authored
- 16 Oct, 2015 1 commit
-
- 15 Oct, 2015 7 commits
-
-
Followings are changed - Changed nodeStore from eventually consistent map to consistent map - Removed ovsdb connection management(ovsdb controller has connection status) - Not only one leader but all onos instances make ovsdb session Following jobs are done - Reads compute node and ovsdb access info from network config - Initiates ovsdb connection to the nodes - Creates integration bridge on each ovsdbs - Creates vxlan tunnel port on each integration bridges Change-Id: I8df4061fcb1eae9b0abd545b7a3f540be50607a9
Hyunsun Moon authored
