Changes between Version 2 and Version 3 of Internal/OpenFlow/Controllers/MultiCtl

Timestamp:

Sep 5, 2012, 8:30:05 PM (12 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Controllers/MultiCtl

@@ -4 +4 @@
 == Quick Links. ==
 [#i Overview] [[BR]]
-[#ii Development Setup] [[BR]]
-[#iii Logs] - records of work [[BR]]
-[#iv Subpages] - extra notes related to this page
+[#ii Logistics] [[BR]]
+[#iii Subpages] - extra notes related to this page [[BR]]
+[#iv Logs] - records of work 
 
 == Overview. == #i
@@ -19 +19 @@
 Developing a general solution to this problem is difficult, so focus will be narrowed down to a more specific task of producing a cooperative multi-controller framework for running a topology configuration service split into a global and local component, and an experimental routing protocol with ID resolution.    
   
-== Development Setup == #ii
+== Logistics == #ii
+==== Work Setup ====
 The [http://yuba.stanford.edu/foswiki/bin/view/OpenFlow/Mininet Mininet SDN prototyping tool] will be used for  testing and debugging implementations. The implementation will be based on modified versions of !OpenFlow Hub's [http://floodlight.openflowhub.org Floodlight controller]. 
 
 Proof-of-concept experiments for evaluating the architecture will be run on ORBIT sandboxes. 
-  
+
+==== Timeline ====
+An approximate 3.5 months (14 weeks) is allotted for design, implementation, and evaluation. the ideal split of time is the following:
+ * 3-5 weeks: architecture layout, topology control, context framework
+ * 3-4 weeks (end of: week 6-9): integrating routing/resolution  
+ * 3-4 weeks (end of: week 9-13): evaluation
+ * remainder (end of: week 14): documentation 
+
+This schedule is a general outline and is used as a guideline; the actual work-flow will inevitably change. 
+ 
+== Subpages == #iii
+
+== Logging. == #iv
+=== (9/5) ===
 ----
 [#home Home.]