Changes between Version 10 and Version 11 of GENIRacksInteroperability


Ignore:
Timestamp:
07/03/12 13:47:03 (12 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIRacksInteroperability

    v10 v11  
    1 = GENI Racks and Meso-scale OpenFlow Interoperability =
     1= GENI Racks and Meso-scale !OpenFlow Interoperability =
    22
    3 This page describes an interoperability experiment that has been completed between Meso-scale !OpenFlow sites, ExoGENI and InstaGENI OpenFlow Resources. This experiment used the !OpenFlow VLAN 1750 was used at each Meso-scale site and the GENI Core !OpenFlow VLAN 3716. In this experiment the following resources are reserved:
     3This page describes an interoperability experiment that has been completed between Meso-scale !OpenFlow sites, ExoGENI and InstaGENI !OpenFlow Resources. This experiment used the !OpenFlow VLAN 1750 was used at each Meso-scale site and the GENI Core !OpenFlow VLAN 3716. In this experiment the following resources are reserved:
    44
    55'''ExoGENI''':
    … …  
    1616 - NRL and Internet2 !OpenFlow VLAN 3716 is used for all hosts in experiment1 to exchange traffic
    1717
    18 The following diagram describes the Meso-scale and GENI Racks interoperability experiment:
     18The following diagram describes the Meso-scale and GENI Racks interoperability experiment captured in this page:
    1919
    2020[[Image(Mesoscale-GENIRacks-interop.jpg,90%)]]
    2121
    22 To simplify the experiment setup, the following aggregate managers nick_names were defined in the omni_config:
     22To simplify the experiment setup, the following aggregate manager nick_names were defined in the omni_config:
    2323
    2424{{{