207 | | {{{ |
208 | | omni.py -a ig-utah createsliver gtwportalslice ~/Downloads/experiments.rspec |
209 | | /usr/local/bin/gcf/examples/readyToLogin.py -a ig-utah gtwportalslice |
210 | | }}} |
211 | | |
212 | | When it is ready, it will give login info in terminal. Log in to client, |
213 | | look in |
214 | | {{{ |
215 | | /tmp/iperf-logs/ |
216 | | }}} |
| 206 | For this step, we'll change the approach a bit and switch to a new client tool: the command line Omni client. If you haven't yet configured Omni, please follow [http://trac.gpolab.bbn.com/gcf/wiki/OmniConfigure/Automatic these instructions] now. |
| 207 | |
| 208 | Once Omni is installed and configured, bringing up the sliver you designed earlier is a one-step procedure. Just enter the command: |
| 209 | |
| 210 | {{{ |
| 211 | $ omni.py -a AM_NICKNAME createsliver SLICENAME RSPEC_FILE |
| 212 | }}} |
| 213 | |
| 214 | where {{{AM_NICKNAME}}} is the nickname for your assigned aggregate manager and {{{SLICENAME}}} is the name of the slice you created at the portal (both of these are given on your worksheet). {{{RSPEC_FILE}}} should be replaced with the filename of the rspec you saved in step 4. |
| 215 | |
| 216 | |
| 217 | If all is well, Omni should give you a number of informational messages, such as: |
| 218 | {{{ |
| 219 | INFO:omni:Loading config file /home/geni/.gcf/omni_config |
| 220 | }}} |
| 221 | |
| 222 | It should quickly proceed to the point where it makes the request to the remote manager: |
| 223 | {{{ |
| 224 | INFO:omni:Creating sliver(s) from rspec file /home/geni/Downloads/experiments.rspec for slice ... |
| 225 | }}} |
| 226 | |
| 227 | This step can sometimes be time-consuming, so please be patient. If it succeeds, within a few minutes Omni should report: |
| 228 | {{{ |
| 229 | INFO:omni: Completed createsliver: |
| 230 | }}} |
| 231 | |
| 232 | and your sliver is complete! |