Changes between Version 16 and Version 17 of Internal/OpenFlow/Controllers/MultiCtl

Timestamp:

Sep 23, 2012, 11:15:33 PM (12 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Controllers/MultiCtl

@@ -144 +144 @@
 With the new resources at hand, we re-document the modifications done to the main Floodlight event handler (Controller.java) in order to intercept and respond to messages from both switches and controller units. 
 
- 1. ''The "server-side" channels.'' A control unit expects two types of incoming connections, 1) from switches, and 2) from other units (peer and downstream). These two are identified by default TCP port values of 6633 and 6644, respectively. The switch channel is handles using OFChannelHandler, which implements the classic !OpenFlow handshake. The unit channel, which we add as the UnitChannelHandler to our Controller.java derivative class (!UnitController.java), deals with the inter-unit handshake, which uses a modified version of !OpenFlow. Both are initialized and added to the same !ChannelGroup when the !UnitController run() method is called.     
+ 1. ''The "server-side" channels.'' A control unit expects two types of incoming connections, 1) from switches, and 2) from other units (peer and downstream). These two are identified by default TCP port values of 6633 and 6644, respectively. The switch channel is handles using OFChannelHandler, which implements the classic !OpenFlow handshake. The unit channel, which we add as the !UnitChannelHandler to our Controller.java derivative class (!UnitController.java), deals with the inter-unit handshake, which uses a modified version of !OpenFlow. Both are initialized and added to the same !ChannelGroup when the !UnitController run() method is called.     
 
- 2. ''client-side channels.'' A controller unit with upstream or peer units will connect to other units as clients. Each client connection is handled by a !UnitConnector, which attempts to connect to each remote socket specified in a topology file located, by default, under resources/ . This file specifies peer and upstream units in separate lists, to facilitate differentiation between the two kinds of server units. We define a unit that accepts connection to be a server unit, and ones connecting, client units. A separate channel handler is supplied for this connections. 
+ 2. ''client-side channels.'' A controller unit with upstream or peer units will connect to other units as clients. Each client connection is handled by a !UnitConnector, which attempts to connect to each remote socket specified in a topology file located, by default, under resources/ . Each entry describing a unit has the following form:
+
+{{{
+        {
+            "name":"unit_name",
+            "host":"localhost",
+            "port": 6644
+        }
+}}}
+ This can of course be easily changed, along with its parser (!UnitConfigUtil.java) and structure holding the information for each entry (!UnitPair.java). This file specifies peer and upstream units in separate lists, in order to facilitate the differentiation between the two kinds of server units. We define a unit that accepts connection to be a server unit, and ones connecting, client units. A separate channel handler is supplied for this connections. 
 
 However, it appears that all three channels use similar-enough channel pipelines, whose only differences lie in which handler is being used; therefore some work to be done in the future include a consolidation of the three !PipelineFactories.