Changes between Version 23 and Version 24 of GENIRacksInteroperability


Ignore:
Timestamp:
07/05/12 15:20:28 (12 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIRacksInteroperability

    v23 v24  
    5555== Interoperability Experiment ==
    5656
    57 The following command were issued to create the slice used for this interoperability experiment:
     57The following command was issued to create the slice used for this interoperability experiment:
    5858{{{
    5959 $ omni.py createslice interop
    … …  
    151151== Run Experiment ==
    152152
    153 Determine which ExoGENI VMs have been assigned to you:
     153Determine which ExoGENI VMs have been assigned to you. Note that for the ExoGENI racks, the list of assigned compute resources can be found with the omni ''listresources'' command:
    154154{{{
    155155 $ omni.py listrsources interop -a exobbn -o
    156156 $ omni.py listresources interop -a exorci -o
    157157}}}
    158 Determine which InstaGENI Utah rack VMs have been assigned to you:
     158Determine which InstaGENI Utah rack VMs have been assigned to you. Note that for the InstaGENI rack, the list of assigned compute resources can be found with the omni ''sliverstatus'' command:
    159159{{{
    160160 $ omni.py sliverstatus interop -a ig -o
    161 
    162161}}}
    163162Determine which PG Utah site VM was associated with VLAN 1750:
    … …  
    172171}}}
    173172
    174 The output files created by the listresources and sliverstatus commands in this section include a "hostname" for each allocated compute resource. Additionally for the PG and InstaGENI VMs there is a port number required to connect.
     173The output files created by the ''listresources'' and ''sliverstatus'' omni commands in this section include a "hostname" for each allocated compute resource. Additionally for the PG and InstaGENI VMs there is a port number required to connect.
    175174
    176 Using information determined from  the listresources and sliverstatus commands was able to login into each compute resource and exchange traffic between all Meso-scale, InstaGENI and ExoGENI compute resources, including the campus resources which were pass through the racks OF Switch.
     175Using information determined from  the ''listresources'' and ''sliverstatus'' commands was able to login into each compute resource shown in the diagram above and exchanged traffic between all Meso-scale, InstaGENI and ExoGENI compute resources, including the campus resources which were configured to pass through the racks OF Switch.
    177176
    178177