Changes between Version 8 and Version 9 of Internal/OpenFlow/FloodlightFVModule

Timestamp:

Jun 14, 2012, 7:37:16 AM (12 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/FloodlightFVModule

@@ -8 +8 @@
 [#s Setup] [[BR]]
 [#bg Background] [[BR]]
-[#a Approach] -  a diary-style log of the implementation
-
+[#a Approach] -  a diary-style log of the implementation [[BR]]
+[#end jump to bottom.] 
 == Overview. == #o
 ''Slicing'' is the SDN (in our case referring to !OpenFlow) term for network virtualization. Specifically, A slice is a SDN controller and the network resources allocated to it by a hypervisor-like entity such as !FlowVisor. With proper resource isolation and allocation, multiple controllers can coexist on a single physical network.     
@@ -124 +124 @@
  * IFloodlightProxy, a copy of IFloodlightProviderService to be used by FVController 
 
-
 '''re-wired files:''' 
  * FVController implements IFloodlightProxy, with FVAcceptor as its version of !FloodlightProvider  
 For the following files, 'rewiring' refers to swapping out IFloodlightProviderService with IFloodlightProxy.
- * ForwardingBase, Forwarding (the generic forwarding components loaded by default) 
+ * !ForwardingBase, Forwarding (the generic forwarding components loaded by default) 
 
 '''additional changes''':
@@ -134 +133 @@
  * Have FVAcceptor subscribe to IFloodlightProviderService as its floodlightprovider
  * Incorporate !FloodlightProvider's functions into FVAcceptor (for now, brutely drop in, just exporting IFloodlightProxy service) 
+
+This process forces the forwarding component to register with FVController, as opposed to the core module. The core module still takes care of !OpenFlow signaling e.g. echo keepalives and the initial handshake, so any switches will still connect properly and keep the connection alive. 
+== . ==#end