Changes between Version 62 and Version 63 of Internal/OpenFlow/Controllers/MultiCtl

Timestamp:

May 13, 2013, 6:23:53 AM (11 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Controllers/MultiCtl

@@ -691 +691 @@
 Current infrastructure contains modules that can find routes (topology) within switches and islands(strongly connected switches) under control of the same controller, but not of different ones. We will call this group of switches/islands a domain. If determined to be out of the domain, current forwarding will flood the message. The route is pulled up by the routing engine(class implementing IRoutingService, which is currently !TopologyManager).   
 
+==== w/o 5/5 - 5/11 ==== #w33 
+Set a deadline of 7/31 for completing everything. This implies:
+ * 1-2 weeks resolver implementation
+ * 4-6 experimentation/testing
+ * 1 full thesis writeup
+
+placing about 6 to 9 weeks of work before the 3-week wait period before defense. This Adds up to between 9 and 11 weeks for own goals, between 7/8 and 7/22.  
+
+==== w/o 5/12 - 5/18 ==== #w34
+Base sanity of resolver and domain mapping checked. Need to test in multi-domain scenarios. Will not work with true internetworks, as no IP is used - this is intended as a pure mock-up.
+
+ Forwarding only needs to use domain information when the destination host is outside of the domain. 
 ----
 [#home Home.]