150 | | <p> |
151 | | |
152 | | <!-----------------------------------------------> |
153 | | |
154 | | <h3>Tell the Configuration Server about your new Nodes</h3> |
155 | | |
156 | | <p> |
157 | | |
158 | | 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. |
| 150 | Note that this is a <em>list</em> of configurations. In JSON, a list is a comma-separated list of times between square brackets like so: [ item, item ..., item ]. Each configuration block is given as a dictionary with the key/value pairs as above. A JSON dictionary is delimited by { }. So a list of dictionaries is [ { ... }, { ... }, ... ]. |
| 151 | |
| 152 | <p> |
| 153 | |
| 154 | <!-----------------------------------------------> |
| 155 | |
| 156 | <h3>3. Tell the Configuration Server about your new Nodes</h3> |
| 157 | |
| 158 | <p> |
| 159 | |
| 160 | The Configuration Server needs to know that information in your brand-new <em>nodes.json</em>file. There's a little script just for this: <em>/share/config_server/bin/initialize_containers.py</em>. This script feeds the information from your <em>nodes.json</em> 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 <em>users</em> machine. |