Changes between Version 32 and Version 33 of NeoContainers

Timestamp:

Oct 22, 2015 12:50:11 PM (9 years ago)

Author:

Geoff Lawler

Comment:

--

NeoContainers

@@ -223 +223 @@
 
 <pre>
-    tb-set-node-os ${pnode(0000)} PNODE-CONT
+    tb-set-node-os ${pnode(0000)} PNODE-BASE
     tb-set-hardware ${pnode(0000)} MicroCloud
 </pre>
-
-<p>
-
-<center>
-<b><i>
-This is straight from the original Neo-Containers documentation, but the
-OS types don't match.<br>
-One line says to use "PNODE_BASE" and the other says
-to use "PNODE-CONT".<br>
-The wrong one must be fixed.
-</i></b>
-</center>
 
 <p>
@@ -324 +312 @@
 <p>
 
-On all the <i>pnode</i>s:
+On all the <i>pnode</i>s which will be running containers:
 
 <pre>
@@ -334 +322 @@
 <p>
 
-<center><b><i>
-Is this needed on <u>all</u> the <i>pnode</i>s or just those that are running containers?
-</i></b></center>
-
-<p>
-
-The <i>pnode</i> role will spawn the containers and configure them.
+The pnode only have to be bootstrapped once per experiment swap in. Once
+a pnode is bootstrapped into chef, <i>chef-client</i> needs to be run.
+
+The <i>pnode</i> role will spawn the containers and configure them. So 
+once the <i>chef-client</i> command is run on a pnode, all containers
+on that be pnode will be running and configured. 
+
+<pre>
+    $ ssh <i>&lt;pnode&gt;</i>.<i>&lt;expid&gt;</i>.<i>&lt;projid&gt;</i>
+    $ cd <i>&lt;config_server-repo&gt;</i>/bin
+    $ sudo chef-client
+</pre>
 
 <p>
@@ -347 +340 @@
 nodes.  Running "sudo chef-client" will re-configure the nodes (both
 <i>pnode</i>s and the containers).
-
-<p>
-
-<center><b><i>
-This is really inspecific.  Are there any limitations to what "sudo
-chef-client" will fix?
-</i></b></center>
 
 <p>
@@ -555 +541 @@
 <p>
 
-<center><b><i>
-What about when the <b>nodes.json</b> changes?  Does the full thing have to
-be re-run?  Is a supplementary JSON file the only thing that must be added?
-Must the experiment be terminated and all the steps started over?
-</i></b></center>
+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>
@@ -626 +611 @@
 <p>
 
-On all the <i>pnode</i>s:
+On all the <i>pnode</i>s which have containers running on them:
 
 <pre>
@@ -635 +620 @@
 
 <p>
-
-<center><b><i>
-Is this needed on <u>all</u> the <i>pnode</i>s or just those that are running containers?
-</i></b></center>
-
-<p>
 It is easy to fix problems if something should go wrong with bootstrapped
 nodes.  Running "sudo chef-client" will re-configure the nodes (both
 <i>pnode</i>s and the containers).
-
-<p>
-
-<center><b><i>
-This is really inspecific.  Are there any limitations to what "sudo
-chef-client" will fix?
-</i></b></center>
 
 <p>