Changes between Version 29 and Version 30 of GiB-gettingStarted


Ignore:
Timestamp:
10/02/12 17:45:18 (7 years ago)
Author:
Vic Thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GiB-gettingStarted

    v29 v30  
    228228In the case of our experiment, the software needed (iperf) was installed by our startup script.  Our startup script put the output of iperf in a file accessible from a web browser.   Since our iperf client ran on node {{{pc101}}} (the node labeled 'left' in the request spec), we can use a browser to view the output of this client.  Start up Firefox in a terminal on the GENI-in-a-Box virtual machine and enter the url {{{http://pc101.geni-in-a-box.net/iperf-client.log}}}.  The iperf client output should appear in your browser window.
    229229
    230 You can also ssh into the node pc102 to view this file.  GENI-in-a-Box comes with a user account 'alice' with private and public keys for alice installed in it.  When experimenter nodes are created an account is created for alice on these nodes and alice's public key installed in the .ssh directory inside alice's home directory.  You can create your own user accounts; see here for instructions.
    231 
    232 You can ssh into node {{{pc101}}} as alice type {{{ssh -lalice pc101.geni-in-a-box.net}}} or just {{{ssh -lalice pc101}}}.  The terminal session below shows the ssh'ing into {{{pc101}}}, going to the directory with the iperf log file, and viewing that file.
     230You can also ssh into the node pc102 to view this file.  GENI-in-a-Box comes with a user account 'alice' with private and public keys for alice installed in it.  When experimenter nodes are created an account is created for alice on these nodes and alice's public key installed in the .ssh directory inside alice's home directory.  You can create your own user accounts; see [wiki:GiB-tips this page] for instructions.
     231
     232You can ssh into node {{{pc101}}} as alice type {{{ssh -lalice pc101.geni-in-a-box.net}}} or just {{{ssh -lalice pc101}}}.  The terminal session below shows the ssh'ing into {{{pc101}}}, going to the directory with the iperf log file, and viewing that file.  The password for alice can be found in {{{~/.gcf/passwords}}}.
    233233{{{
    234234$ ssh -lalice pc101
     
    253253}}}
    254254
     255=== 2.4. Freeing up Resources ===
     256When you are done with your experiment you can return the resources allocated to you using omni's {{{deletesliver}}} command:
     257{{{
     258$ omni.py -a http://geni-in-a-box.net:8001 deletesliver myslice
     259INFO:omni:Loading config file /home/gibuser/.gcf/omni_config
     260INFO:omni:Using control framework gib_ch
     261WARNING:omni:Slice urn:publicid:IDN+geni:gpo:gcf+slice+myslice expires in <= 3 hours
     262INFO:omni:Slice urn:publicid:IDN+geni:gpo:gcf+slice+myslice expires on 2012-10-02 21:55:17 UTC
     263INFO:omni:Deleted sliver urn:publicid:IDN+geni:gpo:gcf+slice+myslice on unspecified_AM_URN at http://geni-in-a-box.net:8001
     264INFO:omni: ------------------------------------------------------------
     265INFO:omni: Completed deletesliver:
     266
     267  Options as run:
     268                aggregate: ['http://geni-in-a-box.net:8001']
     269                framework: gib_ch
     270                getversionCacheName: /home/gibuser/.gcf/get_version_cache.json
     271
     272  Args: deletesliver myslice
     273
     274  Result Summary: Deleted sliver urn:publicid:IDN+geni:gpo:gcf+slice+myslice on unspecified_AM_URN at http://geni-in-a-box.net:8001
     275INFO:omni: ============================================================
     276$
     277}}}
     278
     279Congratulations!  You have successfully run an experiment using GENI-in-a-Box resources!
     280
     281=== 2.4 GENI-in-a-Box Tips ===
     282See [wiki:GiB-tips this page] for tips that you might find helpful while using GENI-in-a-Box.
     283
     284
     285== 3. What's Next? ===
     286You are now ready to run your own experiments inside GENI-in-a-Box.  You might want to start with one of the sample rspecs in the {{{~/geni-in-a-box}}} directory and edit it as needed by your experiment.  See the {{{README}}} file in this directory for a description of the rspecs in this directory.
     287
     288You can [wiki:SignMeUp apply for a GENI account] and use real GENI aggregates and resources for your experiments.  See [wiki:GiB-to-ProtoGENI] for tips on moving your experiment from GENI-in-a-Box to other aggregates (and vice versa).
     289
     290
    255291
    256292[[BR]]
     
    306342
    307343
    308 2. In the terminal window, cd to the directory geni-in-a-box in your home directory and list the contents of that directory.  You will see a number of
    309    
    310 3. List the contents of the directory (ls).  You will see a number of example request rspec files you can use to get started.  We'll walk you through an experiment using one of these rspecs in section [wiki:sampleExperiment].
    311 
    312 4. Before you try running an experiment verify everything is set up right.  Use the http://trac.gpolab.bbn.com/gcf/wiki/Omni omni] experiment tool to list the aggregates available to you: omni.py listaggregates.  This command lists the aggregates registered with the slice authority that ships with GENI-in-a-Box.  You should see one aggregate listed:
    313 
    314 5. Check the version of the GENI AM API implemented by this aggregate: omni.py --