Changes between Version 9 and Version 10 of UsingContainers

Timestamp:

Oct 2, 2012 4:16:50 PM (12 years ago)

Author:

Ted Faber

Comment:

--

UsingContainers

@@ -60 +60 @@
 
 
-
-=== OpenVZ-only and qemu-only auto-partitioned experiments ===
-
-You will need to specify a parameter called "packing". This parameter describes how many qemu virtual nodes will be embedded on each physical node. The host machines have four cores each, so for compute-bound tasks this value should not be higher than 4. For less CPU-intensive tasks we find a factor of 10 to provide adequate performance. This number can in theory be as high as 10 or 20 (perhaps higher).
-
-If you wish for some of your nodes to be realized as physical machines, you must use a TopDL file (not NS) and tag the nodes as physical. Add the attribute {{{benito:node_type = embedded_pnode}}} to any such nodes. See UsingShopdl for documentation on a tool to do this.
-
-Once you have determined the parameters described above, you may start an experiment by logging in to {{{users.isi.deterlab.net}}} and running these commands:
-
-{{{
-$ /share/containers/qemu_experiment.py <PID> <EID> <ns-or-topdl-file> <packing>
-}}}
-
-This will create an [http://openvz.org openvz-]based experiment if {{{--default-container=openvz}}} is given.
-
-=== Mixed mode experiments ===
-
-Mixed mode experiments may only be specified using a TopDL file. Each node must be specially annotated to incdicate its embedding. This is done by specifying an attribute on the node called {{{partition}}}.
-
-The {{{partition}}} attribute specifies the physical node on which a qemu virtual node is realized. This value must be numeric, though there are no restrictions on what numbers are used.
-
-If a node ''lacks'' the {{{partition}}} attribute, it is assumed to be a physical node.
-
-You can use the {{{shopdl.py}}} tool in the {{{util}}} subdirectory of the tree in order to ease manipulation of your TopDL file. See UsingShopdl for more information.
-
-Once you have annotated your TopDL file, you may start an experiment by logging in to {{{users.isi.deterlab.net}}} and running these commands:
-
-{{{
-$ /share/containers/mixed_experiment.py <PID> <EID> <topdl-file>
-}}}
-
 === Creation ===
 
 Upon successful creation, you will be presented with a URL for accessing your experiment via the web interface.
 
-It takes 1-2 minutes for DETER to create the experiment. The creation process has successfully completed once DETER reports "Status: swapped" on the Experiment Activity Log. (The actual output generated by running qemu_experiment.py is "Benito experiment PID/EID successfully created!")
+It takes 1-2 minutes for DETER to create the experiment. The creation process has successfully completed once DETER reports "Status: swapped" on the Experiment Activity Log. (The actual output generated by running containerize.py is "Containerized experiment PID/EID successfully created!")
+
+=== Viewing the Experiment ===
+
+The DETER web interface shows the physical topology that a containerized experiment is embedded in.  This is of some use, but most experimenters want some way to see how their nodes are placed in the physical DETER computers.  The {{{container_image.py}} program can draw simple pictures of containerized experiments and show which physical nodes hold which virtual nodes.
+
+A common way to invoke {{{container_image.py}}} is:
+
+{{{
+$ /share/containers/container_image.py --experiment DeterTest/faber-packem --out packem.png
+}}}
+
+That will result in an image of the topology annotated with node names and IP addresses.  For example, this tcl file:
+
+{{{
+source tb_compat.tcl
+
+set ns [new Simulator]
+source tb_compat.tcl
+
+for { set i 0 } { $i < 10 } { incr i} {
+    set n($i) [$ns node]
+}
+
+set k 0
+for { set i 1} { $i < 10 } { incr i } {
+    set link($i) [ $ns duplex-link $n(0) $n($i) 100Mb 10 ms DropTail]
+}
+
+
+$ns rtproto Static
+$ns run
+}}}
+
+results in this image:
+
 
 == Swapping ==