Changes between Version 39 and Version 40 of NeoContainers

Timestamp:

Nov 23, 2015 1:45:38 PM (8 years ago)

Author:

Geoff Lawler

Comment:

--

NeoContainers

@@ -50 +50 @@
                                                                                                                                                   
 <a name="containers-by-hand"></a>
-<h2>1. Adding virtual machines "by hand" to your experiment.</h2>
+<h2>2. Adding virtual machines "by hand" to your experiment.</h2>
 
 <!----------------------------------------------->
@@ -152 +152 @@
 <!----------------------------------------------->
 
-<h3>Load Containers into DETER</h3>
-
-<p>
-
-DETER must allocate the control network address for the containers prior to
-experiment swap-in.  This allocation occurs by passing the <b>nodes.json</b>
-file to the script at <pre>/share/config_server/bin/initialize_containers.py</pre>.
-
-<p>
-
-This must be run at least once per experiment and <b>must be done before experiment swap-in</b>. This is because the <pre>initialize_containers.py</pre> script asks DETER to allocate control network addresses for the containers. These addresses must exist prior to the containers existing as the control network to request configuration information from the configuration server. And due to the way DETER works, the addresses must be allocated before swap in or the addresses will not be properly associated with the containers hostnames so the configuration server will not be able to talk to the containers.  
-
-The script can be run multiple times without ill effects. 
-
-<p>
-
-The <i>&lt;expid&gt;</i> and <i>&lt;projid&gt;</i> fields in the following
-example are referring to the experiment ID and the project ID.   The
+<h3>Tell the Configuration Server about your new Nodes</h3>
+
+<p>
+
+The Configuration Server needs to know that information in your brand-new <pre>nodes.json</pre>file. There's a little script just for this: <pre>/share/config_server/bin/initialize_containers.py</pre>. This script feeds the information from your <pre>nodes.json</pre> file to the Configuration Server. This must be done <b>before you swap in your experiment<b> for reasons given below. (Note that because the script needs to run before the experiment is swapped in, the script is run on the <pre>users</pre> machine. 
+
+<p>
+
+The script asks DETER to allocate control network addresses for your new nodes. These addresses must exist prior to the containers existing as the control network to request configuration information from the configuration server. And due to the way DETER works, the addresses must be allocated before swap in or the addresses will not be properly associated with the containers hostnames. The hostnames are how the Configuration Server talks to your containers. So if the script is not run, the configuration of the new nodes cannot happen.
+
+The script can be run multiple times without ill effects. The system is smart enough to only request the control network addresses from DETER once. If the script is re-run, the (non-control-net-IP) information will simply overwrite the existing information in the configuration database.
+
+<p>
+
+Below is an example of how to run the script. The <i>&lt;expid&gt;</i> and <i>&lt;projid&gt;</i> fields in the
+example refer to the experiment ID and the project ID.   The
 experiment ID is defined by the user, and could be something like
 "neocont-test" or "netstriping".  The project ID is the name of the project under which the experiment is run.
@@ -179 +177 @@
 </pre>
 
-
-If you decide to change the the nature of the containers run in an experiment,
-you must <b>destroy the experiment</b> and start over. This needs to be done
-so that DETER will unreserve the control net addresses it previously 
-reserved for the containers. 
-
-<p>
+When run, you'll see output in the terminal. If successful, you will not see any <style color="red">[ERROR]</style>s. Here's sample output:
+
 
 <!----------------------------------------------->