Changes between Version 8 and Version 9 of GENIExperimenter/Tutorials/jFed/GettingStarted_PartII_ndn/Procedure/Setup
- Timestamp:
- 07/05/16 16:11:37 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/Tutorials/jFed/GettingStarted_PartII_ndn/Procedure/Setup
v8 v9 21 21 == 1. Design the Experiment == 22 22 23 In today's experiment you will use resources at the aggregate listed on the worksheet. If you don't have a worksheet, use the closest Instagenirack to the first letter of your name (i.e. if your name starts with the letter C, pick a rack that starts with C). This will help to prevent that too many users choose the same rack and eventually the rack will run out of resources.23 In today's experiment you will use resources at the aggregate listed on the worksheet. If you don't have a worksheet, use the closest {{{Instageni}}} rack to the first letter of your name (i.e. if your name starts with the letter C, pick a rack that starts with C). This will help to prevent that too many users choose the same rack and eventually the rack will run out of resources. 24 24 25 25 == 2. Establish the Environment == … … 208 208 209 209 210 === 3.3. Export the modified request RSpec === 210 === 3.3. Modify the RSpec to automatically download scripts and execute commands === 211 GENI allows you to install and execute commands automatically. In the RSpec you have just added there is a tarball with the necessary files and a script that will automatically run when the nodes boot-up.[[br]] 212 For more information about scripts, refer to [http://groups.geni.net/geni/wiki/HowTo/WriteInstallScript Write Install Script] [[br]] 213 To view the commands, please follow the instructions below: 214 215 {{{ 216 #!html 217 <table style="width:100%"> 218 <tr> 219 <td> 220 <ol type='a'> 221 <li>Click on <q>Experimenter</q> node and scroll down to add the link to the tarball (see figure).</li> 222 <li>In the <q>Execute Command</q> 223 </ol> 224 </td> 225 <td align="right"> 226 <img src="http://192.1.242.151/images/ExecuteCommand.png?format=raw" width='200'/> <br/> 227 <b>Figure 3-4</b> Automating your configuration. 228 </td> 229 </tr> 230 </table> 231 }}} 232 233 === 3.4. Export the modified request RSpec === 211 234 Now we will pull back some of the covers and inspect exactly what jFed has been doing for us when preparing the RSpecs for the experiments we design. Each node and link has a corresponding element in the RSpec, and the details of the component configuration (such as the install and execute services we requested above) are specified with attributes, or sometimes child elements, within those portions of the document. 212 235 … … 239 262 240 263 241 === 3. 4. Instantiate the new experiment using Omni ===264 === 3.5. Instantiate the new experiment using Omni === 242 265 243 266 For this step, we'll change the approach a bit and switch to a new client tool, the command line Omni client.