Changes between Version 60 and Version 61 of clusterdvlan


Ignore:
Timestamp:
12/04/09 17:12:13 (12 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • clusterdvlan

    v60 v61  
    275275
    276276
    277 == 5.3.4  First Phase  ==
     277== 5.3.4  First Phase:  Connect Cluster D Aggregates via NLR FrameNet Service ==
    278278
    279279 See Fig 5
     280
    280281 Use NLR Framenet, since a mojority of Cluster D aggregates can connect with it.
     282
    281283 Implement pre-configured (or dynamic) connectivity via NLR and regionals
     284
    282285 Implement dynamic connections at each aggregate.
    283 === 4.1 Ordering of VLAN Connections ===
    284 
    285 Ordering of VLAN connections is likely to proceed from the backbone out to the endpoints:
    286 
    287 a)  In a demo on 7/7/09, the ORCA/BEN project:
    288 •       Used Sherpa to pre-configure VLANs through NLR
    289 •       Pre-assigned VLANs through the Duke campus network
    290 •       And then mapped VLAN tags near the endpoint nodes.
    291 See [[http://groups.geni.net/geni/attachment/wiki/ORCABEN/071509c%20%20ORCA_BEN%20demo.pdf Figures 6-2, 6-3 and 6-4]].
    292 
    293 b)  In a suggested approach to connectivity specification at [[http://groups.geni.net/syseng/wiki/RspecConnectivity RSpec Connectivity]], it is suggested that:  “we give the backbone priority in selecting a network's VLAN ID and aggregates must map the ID within their local network by whatever means is most convenient for them. This way, the experimenter need only know what backbone the aggregate is connected to, and can design the network from there.”
    294 
    295 c)  How will this be done in CLuster D with ORCA?  How will layer 2 ethernet VLANS be terminated and how will they be specified as a dynamic resource?  WIll this be like the July 7 BEN demo? 
    296 
    297 
    298 === 4.2 Static or Dynamic Connections Through Backbone ===
    299 
    300 a)  ProtoGENI (Emulab) uses pre-configured (static) VLANs on Internet2 GENI “wave”, between certain Internet2 Wave System nodes.   
    301 See [[http://www.internet2.edu/waveco/ Internet2]] , [[http://www.protogeni.net/trac/protogeni/wiki/Backbone  ProtoGENI Backbone]] and [[http://www.protogeni.net/trac/protogeni/wiki/BackboneNode   ProtoGENI Backbone Node]]
    302 
    303 b)  ORCA/BEN project pre-configured (static) VLANs using NLR FrameNet service.  See [[http://groups.geni.net/geni/attachment/wiki/ORCABEN/071509c%20%20ORCA_BEN%20demo.pdf  Figures 6-2, 6-3 and 6-4]].
    304 
    305 These were provisioned using Sherpa service. 
    306 
    307 ORCA plans to provide an interface into the Sherpa GCI by 2/1/10, which would allow VLANs in NLR to be dynamically setup.
    308 
    309 Dynamic setup would allow additional flexibility, with some complications.
    310 
    311 A possible first step towards VLAN connectivity is shown in [http://groups.geni.net/geni/attachment/wiki/clusterdvlan/111709b_ClusterD_Connectivity.vsd drawings (visio)] and  [http://groups.geni.net/geni/attachment/wiki/clusterdvlan/Visio-111709b_ClusterD_Connectivity.pdf  drawigns (pdf)] [[BR]]
    312 
    313 === 4.3 Connections Between Backbones ===
    314 
    315 The iGENI (Starlight) crossconnect includes the Starlight L2 crossconnect service in Chicago, which connects to multiple backbone networks, both domestic and international, including NLR and Internet2.
    316 
    317 See [[http://www.startap.net/starlight/NETWORKS/   Starlight]]
    318 
    319 See [[http://www.startap.net/starlight/ENGINEERING/SL-TransLight_5.06.pdf  Starlight GLIF GOLE May, 2006]]
    320 
    321 The Starlight service should be able to bridge connections between multiple backbone networks, allowing access to distant testbeds.  It may be able to bridge VLANs between NLR and Internet2, if allowed.
     286
     287 Ordering of VLAN connections is likely to proceed from the backbone out to the endpoints:
     288  In a demo on 7/7/09, the ORCA/BEN project:
     289  Used Sherpa to pre-configure VLANs through NLR
     290  And then mapped VLAN tags near the endpoint nodes.
     291  See [[http://groups.geni.net/geni/attachment/wiki/ORCABEN/071509c%20%20ORCA_BEN%20demo.pdf Figures 6-2, 6-3 and 6-4]].
     292
     293  In a suggested approach to connectivity specification at [[http://groups.geni.net/syseng/wiki/RspecConnectivity RSpec Connectivity]], it is suggested that:  “we give the backbone priority in selecting a network's VLAN ID and aggregates must map the ID within their local network by whatever means is most convenient for them. This way, the experimenter need only know what backbone the aggregate is connected to, and can design the network from there.”
     294
     295 Dynamic setup would allow additional flexibility, with some complications.
     296
     297
     298== 5.3.5  Second Phase:  Interconnect Backbones via iGENI Crossconnect ==
     299
     300 See Fig 6
     301
     302 The iGENI (Starlight) crossconnect includes the Starlight L2 crossconnect service in Chicago, which connects to multiple backbone networks, both domestic and international, including NLR and Internet2.
     303 See [[http://www.startap.net/starlight/NETWORKS/   Starlight]]
     304 See [[http://www.startap.net/starlight/ENGINEERING/SL-TransLight_5.06.pdf  Starlight GLIF GOLE May, 2006]]
     305 The Starlight service should be able to bridge connections between multiple backbone networks, allowing access to distant testbeds.  It may be able to bridge VLANs between NLR and Internet2, if allowed.