Changes between Version 21 and Version 22 of UsersGuide

Timestamp:

Oct 24, 2012 4:04:12 PM (12 years ago)

Author:

Ted Faber

Comment:

--

UsersGuide

@@ -371 +371 @@
 In return for the greater control on packing, there is a price.  When a set of containers is packed, the containers system takes into account both the nodes to be packed and their interconnections.  When subsets of containers are packed, the system cannot consider the interconnections between subsets.  In some cases, the packing of subsets can lead to a DETER experiment that cannot be created successfully.  This danger is mitigated by the fact that containers that are packed together are often related in ways that limit the number of connections between that set and another.
 
-
+To explore packing, we need a [attachment:example6.tcl larger topology]:
+
+{{{
+source tb_compat.tcl
+set ns [new Simulator]
+
+set center [$ns node]
+tb-add-node-attribute $center "containers:PartitionPass" 0
+
+
+for { set i 1} { $i < 4 } { incr i} {
+    set lanlist $center
+    for { set j 0 } { $j < 20} { incr j } {
+        set idx [expr $i * 20 + $j]
+        set n($idx) [$ns node]
+        tb-add-node-attribute $n($idx) "containers:PartitionPass" $i
+        lappend lanlist $n($idx)
+    }
+    $ns make-lan [join $lanlist " "] 100Mb 0
+}
+
+# Creation boilerplate
+$ns rtptoto Static
+$ns run
+}}}
+
+This creates 3 20-node subnetworks attached to a single central router.  It looks like this:
+
+[[Image(packing-small.png)]]
+
+Each node in the topology is assigned a {{{containers::PackingPass}}} attribute that groups them into subsets.  The {{{conatiners:PackingPass}}} attribute must be assigned an integer value.  The nodes in each packing pass are considered together when packing.  Each pass can be assigned different parameters.  The passes are carried out in order, though that is rarely important.
+
+Our topology assigns 
 
 == Further Reading ==