Changes between Version 28 and Version 29 of GENIRacksInteroperability

Timestamp:

07/05/12 17:56:32 (12 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIRacksInteroperability

@@ -151 +151 @@
 == Run Experiment ==
 
-Determine 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:
+Determine which ExoGENI VMs have been assigned to you at each site. Note that for the ExoGENI racks the list of assigned compute resources can be found with the omni ''listresources'' command:
 {{{
  $ omni.py listrsources interop -a exobbn -o
@@ -171 +171 @@
 }}}
 
-The 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.
-
-Using 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.
+The output files created by the ''listresources'' for ExoGENI and the ''sliverstatus''for InstaGENI include a "hostname" for each allocated compute resource. Additionally for the PG and InstaGENI VMs there is a port number required to connect.
+
+Using 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.
 
 == Aggregates Versions ==