Changes between Version 8 and Version 9 of UsersGuide

Timestamp:

Oct 15, 2012 5:58:37 PM (12 years ago)

Author:

Ted Faber

Comment:

--

UsersGuide

@@ -215 +215 @@
 === Mixing Containers ===
 
-Mixing containers requires the experimenter to assign container types in their topology assignment.  This is done by attaching an attribute to nodes.  The attribute is named {{{containers:node_type}}}.  If the experiment definition is in [http://fedd.isi.deterlab.net/wiki/TopDl topdl] the attribute can be attached using the [http://fedd.deterlab.net/wiki/TopdlLibrary#SharedFunctions standard topdl routines].  Attaching the attribute in ns2 is done using the DETER {{{tb-add-node-attribute}}} command.
+Mixing containers requires the experimenter to assign container types in their topology assignment.  This is done by attaching an attribute to nodes.  The attribute is named {{{containers:node_type}}} it takes the same values as the [UsersGuide#UsingOtherContainerTypes --default-container parameter to containerize.py].  If the experiment definition is in [http://fedd.isi.deterlab.net/wiki/TopDl topdl] the attribute can be attached using the [http://fedd.deterlab.net/wiki/TopdlLibrary#SharedFunctions standard topdl routines].  Attaching the attribute in ns2 is done using the DETER {{{tb-add-node-attribute}}} command.
 
 {{{
@@ -221 +221 @@
 }}}
 
-That command in an ns2 topology description will set {{{node}}} to be placed in an openvz container.  Using this feature, we can modify our [attachment:example1.tcl first topology] to consist of qemu nodes and a single process container in the center.  Process nodes can have unlimited interfaces, but we cannot log into them.  The new topology file looks like this:
+That command in an ns2 topology description will set {{{node}}} to be placed in an openvz container.  Using this feature, we can modify our [attachment:example1.tcl first topology] to consist of qemu nodes and a single process container in the center.  Process nodes can have unlimited interfaces, but we cannot log into them.  The [attachment:example3.tcl new topology file] looks like this:
 
 {{{
@@ -247 +247 @@
 }}}
 
+Because we have explicitly set the {{{container_node_type}}} of each node, the {{{--default-container}}} parameter to {{{containerize.py}}} does nothing.  We can create this experiment using:
+
+{{{
+users:~$ /share/containers/containerize.py  DeterTest example3 ~/example3.tcl 
+Containerized experiment DeterTest/example3 successfully created!
+Access it via http://www.isi.deterlab.net//showexp.php3?pid=DeterTest&eid=example3
+}}}
+
+
+When we swap it in, the experiment will have 10 satellite containers in qemu VMs and a central process that only forwards packets.  Again, you cannot log in to a process container, but you can use the qemu nodes as though they were physical machines.
+
+Another interesting mixture of containers is to put a physical node into the mix.  Here is a modified version of [attachment:example3.tcl our mixed topology] that places the {{{n-9}}} satellite on a physical computer, by setting its {{{containers:node_type}}} to {{embedded_pnode}}}.
+
+After creating that experiment:
+
+{{{
+users:~$ /share/containers/containerize.py  DeterTest example4 ~/example4.tcl Containerized experiment DeterTest/example4 successfully created!
+Access it via http://www.isi.deterlab.net//showexp.php3?pid=DeterTest&eid=example4
+}}}
+
+We can call up the DETER experiment page and look at the visualization tab:
+
+
+
+=== Changing The Packing Factor ===
+