Changes between Version 11 and Version 12 of GENIExperimenter/ExperimentExample-OF-FOAM


Ignore:
Timestamp:
04/03/12 09:34:29 (7 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/ExperimentExample-OF-FOAM

    v11 v12  
    9999 ./src/omni.py -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 listresources -o         # generates rspec-foam-gpolab-bbn-com-3626-foam-gapi-1.xml
    100100}}}
    101  4. NLR and I2 !OpenFlow Core FOAM servers:
    102 {{{
    103 
    104 
    105 }}}
    106 
    107 Note: Each of the omni command used the -o argument to get the listresources output to a file.  Each of the listresources output files are attached to this page.
    108 
    109 
    110 The resulting Advertisement RSpec looks like this:
    111 {{{
    112 #!xml
     101 4. NLR !OpenFlow Core FOAM server:
     102{{{
     103$ ./src/omni.py -a https://foam.nlr.net:3626/foam/gapi/1 -o listresources           # generates rspec-foam-nlr-net-3626-foam-gapi-1.xml
     104
     105}}}
     106
     107Each of the omni command above used the -o argument to get the listresources output to a file, all output files are attached to this page as a reference.  The Advertisement RSpec generated by the listresources are then reviewed to generate the Requests RSpecs to reserve the resources. Information in these files provides the switch and the port URN information to be used in making the OF flowspace reservation. 
     108
     109The above results will give you some insight into what is available, but it is recommended that you coordinate with the site contact to ensure RSpec accuracy for each of the OF Aggregate Managers. 
     110
     111
     112== Compute Resources RSpecs ==
     113
     114The section shows the compute resources RSpec defined based on the output of the listresources commands.
     115
     116'''BBN ProteGENI Compute Resource Rspec '''
     117{{{
    113118<?xml version="1.0" ?>
    114119<!-- Resources at AM:
    115120        URN: unspecified_AM_URN
    116         URL: https://ofam1.site1.com:1443/openflow/gapi/
     121        URL: http://www.pgeni.gpolab.bbn.com/protogeni/xmlrpc/am
    117122 -->
    118 
    119 <rspec type="openflow">
    120   <network location="Somewhere USA " name="local-oim ">
    121     <switches>
    122       <switch urn="urn:publicid:IDN+ofam1.site1.com:expedient:openflow+switch
    123 :06:bb:00:24:88:cc:bb:00">
    124         <port urn="urn:publicid:IDN+ofam1.site1.com:expedient:openflow+switch:044:d0:02:6f:13:f3:b0:0+port:26"/>
    125       </switch>
    126     </switches>
    127     <links/>
    128   </network>
     123<rspec type="request" xmlns="http://www.protogeni.net/resources/rspec/2"
     124        xmlns:emulab="http://www.protogeni.net/resources/rspec/ext/emulab/1"
     125        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     126        xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2 http://www.protogeni.net/resources/rspec/2/request.xsd
     127        http://www.protogeni.net/resources/rspec/ext/emulab/1 http://www.protogeni.net/resources/rspec/ext/emulab/1/ptop_extension.xs
     128d "> 
     129  <node component_id="urn:publicid:IDN+pgeni.gpolab.bbn.com+node+pc5"
     130        component_manager_id="urn:publicid:IDN+pgeni.gpolab.bbn.com+authority+cm"
     131        component_name="pc5" exclusive="true">   
     132      <sliver_type name="raw-pc">     
     133      </sliver_type>   
     134  </node> 
    129135</rspec>
    130136}}}
    131137
    132 
    133 The above provides the switch and the port URN information to be used in making the OF flowspace reservation.  The above results will give you some insight into what is available, but it is recommended that you coordinate with the site contact to ensure RSpec accuracy for each of the OF Aggregate Managers. 
    134 
    135 
    136 
    137 == Request Resources ==
     138''' Clemson MyPLC Compute Resources Rspec'''
     139{{{
     140<?xml version="1.0" ?>
     141<!-- Resources at AM:
     142        URN: unspecified_AM_URN
     143        URL: http://myplc.clemson.edu:12346/
     144 -->
     145<RSpec type="SFA"> 
     146    <network name="plc">   
     147        <node component_id="urn:publicid:IDN+plc:cu+node+planetlab4.clemson.edu"
     148             component_manager_id="urn:publicid:IDN+plc+authority+sa"
     149                node_id="n1" site_id="urn:publicid:IDN+plc:cu+authority+sa">   
     150 
     151            <hostname>        planetlab4.clemson.edu      </hostname>     
     152        </node>   
     153    </network>
     154</RSpec>
     155}}}
     156
     157'''Wisconsin MyPLC Compute Resources RSpec'''
     158{{{
     159<?xml version="1.0" ?>
     160<!-- Resources at AM:
     161        URN: unspecified_AM_URN
     162        URL: https://wings-openflow-1.wail.wisc.edu:12346/
     163 -->
     164<RSpec type="SFA"> 
     165    <network name="plc">   
     166        <node component_id="urn:publicid:IDN+plc:wisc+node+wings-openflow-2.wail.wisc.edu"
     167              component_manager_id="urn:publicid:IDN+plc+authority+sa"
     168                node_id="n9" site_id="urn:publicid:IDN+plc:wisc+authority+sa"> 
     169   
     170            <hostname>        wings-openflow-2.wail.wisc.edu      </hostname>   
     171   
     172        </node>   
     173    </network> 
     174</RSpec>
     175}}}
     176
    138177
    139178The OF RSpecs are used to request resources at each site's !OpenFlow Aggregate Manager.  This will result in your resource request being imported into the Opt-In manager, where an Administrator must approve your request for resources. Currently requesting OF resources for the sites in the experiment does not require OF setup for the Network Core path; the default handling will allow OF traffic.  This is expected to change.