Changes between Version 40 and Version 41 of GENIExperimenter/ExperimentExample
- Timestamp:
- 08/22/12 16:41:43 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/ExperimentExample
v40 v41 22 22 Getting a list of resources from the Emulab ProtoGENI aggregate in GENI v3 rspec format: 23 23 {{{ 24 $ $omni.py -o -a pg-utah listresources -t GENI 324 $ omni.py -o -a pg-utah listresources -t GENI 3 25 25 INFO:omni:Loading config file /home/nriga/.gcf/omni_config 26 26 INFO:omni:Using control framework pg … … 73 73 Getting a list of resources from the !PlanetLab Princeton aggregate in GENI v3 rspec format: 74 74 {{{ 75 $ ./src/omni.py -o -a plc -t geni 3 --api-version 2 listresources75 $ omni.py -o -a plc -t geni 3 --api-version 2 listresources 76 76 INFO:omni:Loading config file /home/nriga/.gcf/omni_config 77 77 INFO:omni:Using control framework pg … … 121 121 }}} 122 122 123 You may use the output of these two ''listresources'' commands to generate rspecs to request resources.123 You may use the output of these two ''listresources'' commands to generate RSpecs to request resources. 124 124 125 125 If you are planning to use MyPLC resources, you may query a MyPLC installation to get a list of available resources as follows: 126 126 {{{ 127 $ ./src/omni.py -o -a plc-gpo listresources127 $ omni.py -o -a plc-gpo listresources 128 128 INFO:omni:Loading config file /home/nriga/.gcf/omni_config 129 129 INFO:omni:Using control framework pg … … 154 154 155 155 {{{ 156 $ ./src/omni.py createslice lnevers-1slice156 $ omni.py createslice lnevers-1slice 157 157 INFO:omni:Loading config file omni_config 158 158 INFO:omni:Using control framework pgeni … … 176 176 177 177 {{{ 178 $ ./src/omni.py renewslice lnevers-1slice 2012-01-30178 $ omni.py renewslice lnevers-1slice 2012-01-30 179 179 INFO:omni:Loading config file omni_config 180 180 INFO:omni:Using control framework pgeni … … 221 221 To 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. 222 222 {{{ 223 $ ./src/omni.py -a pg-utah -o createsliver lnevers-1slice emulab.rspec223 $ omni.py -a pg-utah -o createsliver lnevers-1slice emulab.rspec 224 224 INFO:omni:Loading config file omni_config 225 225 INFO:omni:Using control framework pgeni … … 343 343 344 344 {{{ 345 $ ./src/omni.py -a plc -o createsliver --api-version 2 lnevers-1slice planet.rspec345 $ omni.py -a plc -o createsliver --api-version 2 lnevers-1slice planet.rspec 346 346 INFO:omni:Loading config file omni_config 347 347 INFO:omni:Using control framework pgeni … … 433 433 <login authentication="ssh-keys" hostname="plnode-03.gpolab.bbn.com" port="22" username="pgenigpolabbbncom_lnevers1slice"/> 434 434 </services> 435 lnevers@sendaria:~/gcf-1.5.1$ ./src/omni.py -a pg-utah lnevers-1slice435 $ omni.py -a pg-utah lnevers-1slice 436 436 INFO:omni:Loading config file omni_config 437 437 INFO:omni:Using control framework pgeni … … 521 521 522 522 {{{ 523 $ ./src/omni.py -a plc -o sliverstatus -t geni 3 --api-version 2 lnevers-1slice523 $ omni.py -a plc -o sliverstatus -t geni 3 --api-version 2 lnevers-1slice 524 524 INFO:omni:Loading config file omni_config 525 525 INFO:omni:Using control framework pgeni … … 575 575 576 576 {{{ 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' 578 578 INFO:omni:Loading config file omni_config 579 579 INFO:omni:Using control framework pgeni … … 599 599 600 600 {{{ 601 $ ./src/omni.py -a pg-utah sliverstatus lnevers-1slice601 $ omni.py -a pg-utah sliverstatus lnevers-1slice 602 602 INFO:omni:Loading config file omni_config 603 603 INFO:omni:Using control framework pgeni … … 624 624 625 625 == Find Slivers and List Resources in your Slice == 626 626 627 If 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. 627 628 628 629 Run: 629 630 {{{ 630 $ ./src/omni.py -a pg-utah -o -t ProtoGENI 2 listresources lnevers-1slice631 $ omni.py -a pg-utah -o -t ProtoGENI 2 listresources lnevers-1slice 631 632 INFO:omni:Loading config file omni_config 632 633 INFO:omni:Using control framework pgeni … … 681 682 When 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: 682 683 {{{ 683 $ ./src/omni.py -a pg-utah deletesliver lnevers-1slice684 $ omni.py -a pg-utah deletesliver lnevers-1slice 684 685 INFO:omni:Loading config file omni_config 685 686 INFO:omni:Using control framework pgeni … … 711 712 For example: 712 713 {{{ 713 $ ./src/omni.py -a plc deletesliver -t geni 3 --api-version 2 lnevers-1slice714 $ omni.py -a plc deletesliver -t geni 3 --api-version 2 lnevers-1slice 714 715 INFO:omni:Loading config file omni_config 715 716 INFO:omni:Using control framework pgeni … … 733 734 Then, to see what resources you have in this slice at Planetlab: 734 735 {{{ 735 $ ./src/omni.py -f pgeni -a plc -t geni 3 --api-version 2 listresources lnevers-1slice736 $ omni.py -f pgeni -a plc -t geni 3 --api-version 2 listresources lnevers-1slice 736 737 }}} 737 738