| | 1 | == 1. Establish test/experiment environment == |
| | 2 | |
| | 3 | === User Workspace === |
| | 4 | * Using the GEC14 Tutorial VM |
| | 5 | * Inputs: |
| | 6 | * GENI certificate |
| | 7 | * installed in $HOME/.ssl |
| | 8 | * location configured in omni_config |
| | 9 | * stripped the passphrase for automation |
| | 10 | * SSH key pair |
| | 11 | * installed in $HOME/.ssh |
| | 12 | * location configured in omni_config |
| | 13 | * key added to ssh-agent |
| | 14 | * iRODS account |
| | 15 | * username configured in $HOME/.irods/.irodsEnv |
| | 16 | * password stored using iinit |
| | 17 | * All credentials configured using credconfig.sh script |
| | 18 | * Outputs: |
| | 19 | * omni.py ready to use |
| | 20 | * i-commands ready to use |
| | 21 | * ready to log into nodes in the slice |
| | 22 | |
| | 23 | === iRODS server === |
| | 24 | * iRODS server on emmy8 was down so I set up my own on pc41.emulab.net |
| | 25 | |
| | 26 | === OML server === |
| | 27 | * Set up my own OML server on pc41.emulab.net |
| | 28 | * I was not able to get the oml2-server to use the hook script when started as a service (/etc/init.d/oml2-server start) - only when started on the command line: |
| | 29 | {{{ |
| | 30 | $ oml2-server --listen=3003 --data-dir=/users/johren/gimi --logfile=/users/johren/oml_server.log -H /users/johren/oml2-server-hook.sh |
| | 31 | }}} |
| | 32 | * Configured hook script to use my iRODS server |
| | 33 | |
| | 34 | == 2. Obtain slice of GENI resources, install and configure GIMI I&M tools == |
| | 35 | * Used omni to create the slice and the sliver on ExoSM aggregate |
| | 36 | * rspec link here |
| | 37 | * Rspec includes an execute service for each node that downloads [http://pc41.emulab.net/gimi-postboot.sh gimi-postboot.sh] from the web server (on pc41.emulab.net) and runs it with the slicename and nodeid parameters |
| | 38 | {{{ |
| | 39 | <services> |
| | 40 | <execute command="wget -q -P /tmp http://pc41.emulab.net/gimi-postboot.sh ;chmod +x /tmp/gimi-postboot.sh;/tmp/gimi-postboot.sh %SLICENAME% NodeB > /tmp/gimi-postboot.log" shell="/bin/sh"/> |
| | 41 | </services> |
| | 42 | }}} |
| | 43 | |
| | 44 | == 3. Run and orchestrate GIMI I&M tools and reference/actual experiment == |
| | 45 | * Run the tcp_iperf.rb script using the EC on the UW VM |
| | 46 | {{{ |
| | 47 | $ omf-5.4 exec --no-cmc -S johGIM1208011452 tcp_iperf.rb -- --source1 johGIM1208011452-NodeA --sink johGIM1208011452-NodeC |
| | 48 | }}} |
| | 49 | |
| | 50 | |
| | 51 | == 4. Push I&M measurement results to iRODS archive service == |
| | 52 | |
| | 53 | == 6. Pull I&M measurement results from iRODS archive service to UW == |
| | 54 | |
| | 55 | == 5. Observe I&M measurement results on GIMI presentation service == |
| | 56 | |
| | 57 | |
| | 58 | |
| | 59 | == 7. Release resources, and cleanup == |
