Changes between Version 23 and Version 24 of Internal/OpenFlow/Controllers/MultiCtl

Timestamp:

Oct 7, 2012, 9:26:55 PM (13 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Controllers/MultiCtl

@@ -201 +201 @@
  * Slices: these are designed to keep controllers that conflict with each other in separate pools of network resource, allowing each to exist as if they are the only controllers in the network. This effect is achieved thanks to a proxy, not collaboration between the controllers.    
 
+==== (10/5) ====
+A test implementation of the switch-side handshake was added to the codebase, in a separate package `net.floodlightcontroller.core.misc`. This is a client-side !ChannelHandler/!PipelineFactory that generates switch-side handshake reply messages and ECHO_REPLIES to keepalive pings once it completes the handshake. This will be used as a base for the controller's client components. 
+
+Noting initialization, the handler's channel is set manually during client startup:
+{{{
+  /*In client class*/ 
+  
+  OFClientPipelineFactory cfact = new OFClientPipelineFactory(null);
+  final ClientBootstrap cb = createClientBootStrap();
+  cb.setPipelineFactory(cfact);
+  InetSocketAddress csa = new InetSocketAddress(this.remote, this.port);
+  ChannelFuture future = cb.connect(csa);
+            
+  Channel channel = future.getChannel();
+  cfact.setHandlerChannel(channel);
+}}}    
+This can probably be avoided if the handler is implemented as an inner class to the client class that fires up the channel, as in Controller.java. 
+
+
 ----
 [#home Home.]