Changes between Version 2 and Version 3 of SAW


Ignore:
Timestamp:
06/21/12 15:47:20 (7 years ago)
Author:
hdempsey@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SAW

    v2 v3  
    66A GENI engineering summary (GENI-centric view)
    77
    8 A [http://groups.geni.net/syseng/attachment/wiki/SAW/Slice%20Around%20The%20World%20Demonstration%20Description%20V1.doc general description] without much engineering content is attached to this page.  It lists all the labs that intend to be part of the SAW demo in some way.  A one-sentence summary is that Starlight will engineer VLANs that span many different international research labs that have projects in network virtualization, and those projects will collaborate to run high-touch applications over dynamic processing and network resources.  The first application is supposed to be scientific visualization for distributed computing associated with nanotechnology experiments.
     8A [http://groups.geni.net/syseng/attachment/wiki/SAW/Slice%20Around%20The%20World%20Demonstration%20Description%20V1.doc general description] is attached to this page.  It lists all the labs that intend to be part of the SAW demo in some way.  A one-sentence summary of the demo is that Starlight will engineer VLANs that span many different international research labs that have projects in network virtualization, and those projects will collaborate to run high-touch applications over dynamic processing and network resources.  The first application is supposed to be scientific visualization for distributed computing associated with nanotechnology experiments.
    99
    1010A [http://groups.geni.net/syseng/attachment/wiki/SAW/SATW-VLAN.pdf partial network diagram] showing connections between Japan, Internet2 ION, ProtoGENI Utah (only) and NREN/Starlight (show as GENI cloud) illustrates how four non-GENI VLANs (1517, 1591, 1592, 1595) will be used.  These VLANs do not overlap with any GENI mesoscale VLANs, but they do use the same ION ports that many GENI mesoscale connections use.  The initial estimated size of these VLANs was 10Gbps, but they probably cannot be implemented at that speed end-to-end, due to shared resource constraints such as ION.