Changes between Version 40 and Version 41 of GENIExperimenter/ExperimentExample


Ignore:
Timestamp:
08/22/12 16:41:43 (12 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/ExperimentExample

    v40 v41  
    2222Getting a list of resources from the Emulab ProtoGENI aggregate in GENI v3 rspec format:
    2323{{{
    24 $$ omni.py -o -a pg-utah listresources -t GENI 3
     24$ omni.py -o -a pg-utah listresources -t GENI 3
    2525INFO:omni:Loading config file /home/nriga/.gcf/omni_config
    2626INFO:omni:Using control framework pg
     
    7373Getting a list of resources from the !PlanetLab Princeton aggregate in GENI v3 rspec format:
    7474{{{
    75 $ ./src/omni.py -o -a plc -t geni 3 --api-version 2 listresources
     75$ omni.py -o -a plc -t geni 3 --api-version 2 listresources
    7676INFO:omni:Loading config file /home/nriga/.gcf/omni_config
    7777INFO:omni:Using control framework pg
     
    121121}}}
    122122
    123 You may use the output of these two ''listresources'' commands to generate rspecs to request resources.
     123You may use the output of these two ''listresources'' commands to generate RSpecs to request resources.
    124124
    125125If you are planning to use MyPLC resources, you may query a MyPLC installation to get a list of available resources as follows:
    126126{{{
    127 ./src/omni.py -o -a plc-gpo listresources
     127omni.py -o -a plc-gpo listresources
    128128INFO:omni:Loading config file /home/nriga/.gcf/omni_config
    129129INFO:omni:Using control framework pg
     
    154154
    155155{{{
    156 ./src/omni.py createslice lnevers-1slice
     156omni.py createslice lnevers-1slice
    157157INFO:omni:Loading config file omni_config
    158158INFO:omni:Using control framework pgeni
     
    176176
    177177{{{
    178 ./src/omni.py renewslice lnevers-1slice 2012-01-30
     178omni.py renewslice lnevers-1slice 2012-01-30
    179179INFO:omni:Loading config file omni_config
    180180INFO:omni:Using control framework pgeni
     
    221221To request two ProtoGENI nodes, a sliver was created within the Emulab ProtoGENI aggregate with the RSpec above using the following command. Note the use of the {{{-o}}} argument, which saves the manifest RSpec to a file. The manifest contains your new host's IP address and login information.
    222222{{{
    223 $  ./src/omni.py -a pg-utah -o createsliver lnevers-1slice emulab.rspec
     223$ omni.py -a pg-utah -o createsliver lnevers-1slice emulab.rspec
    224224INFO:omni:Loading config file omni_config
    225225INFO:omni:Using control framework pgeni
     
    343343
    344344{{{
    345 $  ./src/omni.py -a plc -o createsliver --api-version 2  lnevers-1slice planet.rspec
     345$ omni.py -a plc -o createsliver --api-version 2  lnevers-1slice planet.rspec
    346346INFO:omni:Loading config file omni_config
    347347INFO:omni:Using control framework pgeni
     
    433433            <login authentication="ssh-keys" hostname="plnode-03.gpolab.bbn.com" port="22" username="pgenigpolabbbncom_lnevers1slice"/>     
    434434        </services>   
    435 lnevers@sendaria:~/gcf-1.5.1$ ./src/omni.py -a pg-utah lnevers-1slice
     435$ omni.py -a pg-utah lnevers-1slice
    436436INFO:omni:Loading config file omni_config
    437437INFO:omni:Using control framework pgeni
     
    521521
    522522{{{
    523 $ ./src/omni.py -a plc -o sliverstatus -t geni 3 --api-version 2 lnevers-1slice
     523$ omni.py -a plc -o sliverstatus -t geni 3 --api-version 2 lnevers-1slice
    524524INFO:omni:Loading config file omni_config
    525525INFO:omni:Using control framework pgeni
     
    575575
    576576{{{
    577 $ ./src/omni.py -a pg-utah renewsliver lnevers-1slice '2012-01-14 16:10:10'
     577$ omni.py -a pg-utah renewsliver lnevers-1slice '2012-01-14 16:10:10'
    578578INFO:omni:Loading config file omni_config
    579579INFO:omni:Using control framework pgeni
     
    599599
    600600{{{
    601 $ ./src/omni.py -a pg-utah sliverstatus lnevers-1slice
     601$ omni.py -a pg-utah sliverstatus lnevers-1slice
    602602INFO:omni:Loading config file omni_config
    603603INFO:omni:Using control framework pgeni
     
    624624
    625625== Find Slivers and List Resources in your Slice ==
     626
    626627If at any point you forget what you have reserved in your slice, or lose the manifest RSpec that you saved earlier, you can retrieve it. By calling ''listresources'' with your slice name as an argument, you get your manifest RSpec again.
    627628
    628629Run:
    629630{{{
    630 $ ./src/omni.py -a pg-utah -o -t ProtoGENI 2 listresources lnevers-1slice
     631$ omni.py -a pg-utah -o -t ProtoGENI 2 listresources lnevers-1slice
    631632INFO:omni:Loading config file omni_config
    632633INFO:omni:Using control framework pgeni
     
    681682When the experiment is completed you should release the resources by deleting the resource sliver for each of the Resource Aggregates used in the Experiment. In the example experiment used in this page, the ProtoGENI sliver was deleted as follows:
    682683{{{
    683 $ ./src/omni.py -a pg-utah deletesliver lnevers-1slice
     684$ omni.py -a pg-utah deletesliver lnevers-1slice
    684685INFO:omni:Loading config file omni_config
    685686INFO:omni:Using control framework pgeni
     
    711712For example:
    712713{{{
    713 $ ./src/omni.py -a plc deletesliver  -t geni 3 --api-version 2 lnevers-1slice
     714$ omni.py -a plc deletesliver  -t geni 3 --api-version 2 lnevers-1slice
    714715INFO:omni:Loading config file omni_config
    715716INFO:omni:Using control framework pgeni
     
    733734Then, to see what resources you have in this slice at Planetlab:
    734735{{{
    735 $ ./src/omni.py -f pgeni -a plc -t geni 3 --api-version 2 listresources lnevers-1slice
     736$ omni.py -f pgeni -a plc -t geni 3 --api-version 2 listresources lnevers-1slice
    736737}}}
    737738