Changes between Version 36 and Version 37 of GENIExperimenter/ExperimentExample


Ignore:
Timestamp:
08/22/12 15:05:27 (7 years ago)
Author:
nriga@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/ExperimentExample

    v36 v37  
    7373Getting a list of resources from the !PlanetLab Princeton aggregate in GENI v3 rspec format:
    7474{{{
    75 $  ./src/omni.py -o -a http://www.planet-lab.org:12346 -t geni 3 --api-version 2 listresources
    76 INFO:omni:Loading config file omni_config
    77 INFO:omni:Using control framework pgeni
     75$ ./src/omni.py -o -a plc -t geni 3 --api-version 2 listresources
     76INFO:omni:Loading config file /home/nriga/.gcf/omni_config
     77INFO:omni:Using control framework pg
    7878INFO:omni:Saving output to a file.
     79INFO:omni:Substituting AM nickname plc with URL https://www.planet-lab.org:12346, URN unspecified_AM_URN
    7980INFO:omni:Listed resources on 1 out of 1 possible aggregates.
    8081INFO:omni:Writing to 'rspec-www-planet-lab-org.xml'
     
    8384
    8485  Options as run:
    85                 aggregate: http://www.planet-lab.org:12346
    86                 api_version: 2
    87                 framework: pgeni
    88                 native: True
    89                 output: True
    90                 rspectype: ('geni', '3')
     86                aggregate: plc
     87                api_version: 2
     88                framework: pg
     89                native: True
     90                output: True
     91                rspectype: ('geni', '3')
    9192
    9293  Args: listresources
     94
    9395  Result Summary: Retrieved resources from 1 aggregates.
    9496Wrote rspecs from 1 aggregates to 1 files
    95 Saved listResources RSpec at unspecified_AM_URN to file rspec-www-planet-lab-org.xml.
     97Saved listresources RSpec at 'unspecified_AM_URN' to file rspec-www-planet-lab-org.xml; .
    9698INFO:omni: ============================================================
    9799}}}
     
    119121}}}
    120122
    121 You may use the output of these two ''listresources'' commands to generate rspecs to request resources. The above ''listresources'' commands use the default native rspec format rather than the deprecated omnispec format. Note that with native RSpecs, the {{{-a}}} flag or the {{{aggregates}}} entry in your {{{omni_config}}} is required to specify an aggregate manager.   
     123You may use the output of these two ''listresources'' commands to generate rspecs to request resources.
    122124
    123125If you are planning to use MyPLC resources, you may query a MyPLC installation to get a list of available resources as follows:
    124126{{{
    125 $  ./src/omni.py -a http://myplc.gpolab.bbn.com:12346 -o listresources
    126 INFO:omni:Loading config file omni_config
    127 INFO:omni:Using control framework pgeni
     127$  ./src/omni.py -o -a plc-gpo listresources
     128INFO:omni:Loading config file /home/nriga/.gcf/omni_config
     129INFO:omni:Using control framework pg
    128130INFO:omni:Saving output to a file.
     131INFO:omni:Substituting AM nickname plc-gpo with URL http://myplc.gpolab.bbn.com:12346/, URN unspecified_AM_URN
    129132INFO:omni:Listed resources on 1 out of 1 possible aggregates.
    130 INFO:omni:Writing to 'rspec-myplc-gpolab-bbn-com.xml'
     133INFO:omni:Writing to 'rspec-myplc-gpolab-bbn-com-12346-.xml'
    131134INFO:omni: ------------------------------------------------------------
    132135INFO:omni: Completed listresources:
    133136
    134137  Options as run:
    135                 aggregate: http://myplc.gpolab.bbn.com:12346
    136                 framework: pgeni
    137                 native: True
    138                 output: True
     138                aggregate: plc-gpo
     139                framework: pg
     140                native: True
     141                output: True
    139142
    140143  Args: listresources
     
    142145  Result Summary: Retrieved resources from 1 aggregates.
    143146Wrote rspecs from 1 aggregates to 1 files
    144 Saved listResources RSpec at unspecified_AM_URN to file rspec-myplc-gpolab-bbn-com.xml.
    145 INFO:omni: ============================================================
    146 }}}
    147 
    148 If you are planning to use University of Kentucky Emulab resources, you can query just this installation (instead of all PG aggregates, as we did in the example above) to get a list of available resources. Note the example below was collected with GPO pgeni.gpolab.bbn.com credentials:
    149 {{{
    150 $  ./src/omni.py -a https://www.uky.emulab.net/protogeni/xmlrpc/am -o listresources
    151 INFO:omni:Loading config file omni_config
    152 INFO:omni:Using control framework pgeni
    153 INFO:omni:Saving output to a file.
    154 INFO:omni:Listed resources on 1 out of 1 possible aggregates.
    155 INFO:omni:Writing to 'rspec-www-uky-emulab-net-protogeni.xml'
    156 INFO:omni: ------------------------------------------------------------
    157 INFO:omni: Completed listresources:
    158 
    159   Options as run:
    160                 aggregate: https://www.uky.emulab.net/protogeni/xmlrpc/am
    161                 framework: pgeni
    162                 native: True
    163                 output: True
    164 
    165   Args: listresources
    166 
    167   Result Summary: Retrieved resources from 1 aggregates.
    168 Wrote rspecs from 1 aggregates to 1 files
    169 Saved listResources RSpec at unspecified_AM_URN to file rspec-www-uky-emulab-net-protogeni.xml.
     147Saved listresources RSpec at 'unspecified_AM_URN' to file rspec-myplc-gpolab-bbn-com-12346-.xml; .
    170148INFO:omni: ============================================================
    171149}}}
     
    173151== Create a slice ==
    174152
    175 Since the [wiki:GENIExperimenter/ExperimentExample#OmniConfiguration omni_config] specifies using the credentials and the Clearinghouse for the GPO ProtoGENI, your slice will be created in the pgeni.gpolab.bbn.com namespace.  For this example a slice named ''lnevers-1slice'' is created; you should choose a slice name that is meaningful to you. To avoid confusion, avoid creating a slice with the same name as your username (ie if your username is ''lnevers'', don't name your slice ''lnevers'' too).
     153If you have an account with GPO's Clearinghouse then your slice will be created in the pgeni.gpolab.bbn.com namespace.  For this example a slice named ''lnevers-1slice'' is created; you should choose a slice name that is meaningful to you. To avoid confusion, avoid creating a slice with the same name as your username (ie if your username is ''lnevers'', don't name your slice ''lnevers'' too).
    176154
    177155{{{
     
    195173== Renew your slice ==
    196174
    197 Note in the above output that our new slice expires soon. Your resource reservations will not be longer then your slice life, and will go away when the reservation expires. For your experiment be sure to renew your slice for the duration of your experiment. Here we only slightly extend the slice lifetime.
     175Note in the above output that our new slice expires soon. Any resources that you will reserve as part of your slice can not last longer than your slice, and will go away when the reservation expires. For your experiment be sure to renew your slice for the duration of your experiment. Here we only slightly extend the slice lifetime.
    198176
    199177{{{
     
    218196}}}
    219197
    220 == Add Emulab PG resources to GPO PG slice ==
     198== Add Emulab PG resources to your slice ==
    221199
    222200To request two Emulab ProtoGENI nodes, the following rspec named emulab.rspec was used for this example; your rspec will be specific to your experiment requirements:
     
    243221To 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.
    244222{{{
    245 $  ./src/omni.py -a https://www.emulab.net/protogeni/xmlrpc/am -o createsliver lnevers-1slice emulab.rspec
     223$  ./src/omni.py -a pg-utah -o createsliver lnevers-1slice emulab.rspec
    246224INFO:omni:Loading config file omni_config
    247225INFO:omni:Using control framework pgeni
     
    276254 -->
    277255
    278 <rspec type="manifest" xmlns="http://www.protogeni.net/resources/rspec/2" xmlns:emulab="http://www.protogeni.net/resources/rspec/ext/emulab/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2 http://www.protogeni.net/ resources/rspec/2/request.xsd http://www.protogeni.net/resources/rspec/ext/emulab/1 http://www.protogeni.net/resources/rspec/ext/emulab/1/ptop _extension.xsd"> 
    279     <node component_id="urn:publicid:IDN+emulab.net+node+pc333" component_manager_id="urn:publicid:IDN+emulab.net+authority+cm" exclusive="true" sliver_id="urn:publicid:IDN+emulab.net+sliver+68392" virtual_id="geni1" virtualization_type="emulab-vnode" xmlns:emulab="http://www.protogeni.net/resources/rspec/ext/emulab/1">   
    280       <sliver_type name="raw-pc"/>    <emulab:vnode name="pc333"/>    <host name="geni1.lnevers-1slice.pgeni-gpolab-bbn-com.emulab.net"/>    <services>      <login authentication="ssh-keys" hostname="pc333.emulab.net" port="22" username="lnevers"/>    </services>  </node> 
     256<rspec type="manifest"
     257       xmlns="http://www.protogeni.net/resources/rspec/2"
     258       xmlns:emulab="http://www.protogeni.net/resources/rspec/ext/emulab/1"
     259       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     260       xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2
     261                            http://www.protogeni.net/ resources/rspec/2/request.xsd
     262                            http://www.protogeni.net/resources/rspec/ext/emulab/1
     263                            http://www.protogeni.net/resources/rspec/ext/emulab/1/ptop _extension.xsd"> 
     264    <node component_id="urn:publicid:IDN+emulab.net+node+pc333"
     265          component_manager_id="urn:publicid:IDN+emulab.net+authority+cm"
     266          exclusive="true" sliver_id="urn:publicid:IDN+emulab.net+sliver+68392"
     267          virtual_id="geni1" virtualization_type="emulab-vnode"
     268          xmlns:emulab="http://www.protogeni.net/resources/rspec/ext/emulab/1">   
     269     
     270         <sliver_type name="raw-pc"/>   
     271         <emulab:vnode name="pc333"/>   
     272         <host name="geni1.lnevers-1slice.pgeni-gpolab-bbn-com.emulab.net"/>   
     273         <services>     
     274                  <login authentication="ssh-keys" hostname="pc333.emulab.net" port="22" username="lnevers"/>   
     275         </services> 
     276   </node> 
    281277    <node component_id="urn:publicid:IDN+emulab.net+node+pc350" component_manager_id="urn:publicid:IDN+emulab.net+authority+cm" exclusive="true" sliver_id="urn:publicid:IDN+emulab.net+sliver+68393" virtual_id="geni2" virtualization_type="emulab-vnode" xmlns:emulab="http://www.protogeni.net/resources/rspec/ext/emulab/1">   
    282278      <sliver_type name="raw-pc"/>    <emulab:vnode name="pc350"/>    <host name="geni2.lnevers-1slice.pgeni-gpolab-bbn-com.emulab.net"/>    <services>      <login authentication="ssh-keys" hostname="pc350.emulab.net" port="22" username="lnevers"/>    </services>  </node> 
     
    288284To request three PlanetLab nodes, the following rspec named planet.rspec was used for this example; your rspec will be specific to your experiment requirements.
    289285
    290 This example uses ProtoGENI V2 RSpec format. Standard SFA formats are also acceptable. To generate the ProtoGENI V2 request from the Advertisement:
     286This example uses ProtoGENI V2 RSpec format, to generate the ProtoGENI V2 request from the Advertisement:
    291287 * Change the rspec headers to specify that this is a request, using the headers shown below
    292288 * Pull out only the nodes you wish to reserve - ensure they say {{{available now="true"}}}