Changes between Version 42 and Version 43 of Internet Scale Overlay Hosting


Ignore:
Timestamp:
04/05/10 11:11:22 (10 years ago)
Author:
Jon Turner
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Internet Scale Overlay Hosting

    v42 v43  
    8080[http://www.arl.wustl.edu/~jst/pubs/ancs06-turner.pdf ANCS 2006 Paper on a GENI Backbone Platform Architecture] [[BR]]
    8181 
    82 == Spiral 1 Connectivity ==
     82== Current Deployment (as of 11/2009) ==
    8383
    84 SPP Nodes will be located at Internet2 backbone sites.  Five sites are currently planned for GENI (see [http://groups.geni.net/geni/attachment/wiki/presentations/gec-Turner_2008-10.ppt the plan briefed at GEC3].  SPP nodes will tag outgoing packets with VLAN tags and will
    85 expect VLAN tags on input. However, it will will not perform VLAN switching. To view an SPP node configuration with connection requirements [http://groups.geni.net/geni/attachment/wiki/OverlayHostingNodes/SPP_gpoNodeConfig.pdf click here.]     
     84SPP Nodes are currently located at three Internet2 backbone sites - Salt Lake City, Kansas City and Houston.
     85Additional systems will be installed in Atlanta and Houston in the second or third quarter of 2010.
     86Each of the three current SPPs is connected by a pair of 1 Gb/s links, implemented using a static
     87point-to-point VLAN. These are routed through the proto-GENI
     88switch at each site, onto optical links provided by Internet 2.
     89Each of the three SPPs also has three 1 Gb/s links to the Internet 2 router at its site.
     90VLAN tags are used to route these connections through an I2 switch to the router.
     91The SPP VLAN tags are used purely for routing through the connecting components and
     92are not visible to GENI researchers.
     93To view an SPP node configuration with connection requirements
     94[http://groups.geni.net/geni/attachment/wiki/OverlayHostingNodes/SPP_gpoNodeConfig.pdf click here.]     
    8695
    8796''Size & Power Specifications''[[BR]]
    88 The current status for the SPP node looks like this:
    89 ATCA Chassis: 6U rack space, 1200W -48V power, max (via two 1/4“ - 20 UNC studs). It is capable of using two, redundant power sources, if available. Each would need to be rated for at least 25A @ -48V. [[BR]]
     97ATCA Chassis: 6U rack space, 1200W -48V power, max (via two 1/4“ - 20 UNC studs). The
     98chassis is capable of using two, redundant power sources, if available. Each would need to be rated for at least 25A @ -48V. [[BR]]
    9099Power Supply: 1U rack space, one NEMA 5-15 receptacle(if -48V is not available, this power supply will provide it)[[BR]]
    91100Control Processor: 1U rack space, one NEMA 5-15 receptacle (650W max)[[BR]]
     
    96105''IP addresses''
    97106
    98 Each SPP will connect to a local Internet 2 router, using multiple 1 GbE connections.
    99 The number of such connections per site will vary from 2 to 4.
    100 Each will need an I2 IP address for each such interfaces. These addresses should be advertised to I2-connected
    101 universities, but need not be advertised to the public Internet.
    102 Each SPP will also require a separate connection from its control processor. This can be a low bandwidth (10/100 Mb/s)
    103 connection, and should be accessible from any I2-connected university. Public addresses have been requested from Internet2.
     107Each SPP has an IP address for each of its interfaces. For the interfaces connected to the I2 router,
     108these addresses are public and routable from any I2 connected organization. They are generally not
     109routable from arbitrary locations in the Internet. For the interfaces used to directly connect to other SPPs,
     110the IP addresses are private and have no significance for Internet routing. Howeve3r, when configuring an
     111experiment on an SPP node, these addresses are used to identify the interface of interest.
     112The IP addresses for the currently deployed nodes are shown in the figure below.
    104113
    105 IP connectivity between the PlanetLab clearinghouse and the SPP nodes is required.
     114[[Image(sppInterfaces.png, 50%)]]
    106115
    107116''Layer 2 connections''
    108117
    109 Layer 2 virtual Ethernets between the Gigabit Ethernet switches at all all deployed SPP nodes in Internet2 are required (see [http://groups.geni.net/geni/attachment/wiki/OverlayHostingNodes/SPP_gpoNodeConfig.pdf SPP interface block diagram].  The !NetGear GSM7328S with a 10GbE module is a likely candidate for the  Gigabit Ethernet switch.  
     118Layer 2 virtual Ethernets between the Gigabit Ethernet switches at all all deployed SPP nodes in Internet2 are required (see [http://groups.geni.net/geni/attachment/wiki/OverlayHostingNodes/SPP_gpoNodeConfig.pdf SPP interface block diagram].  The !NetGear GSM7328S with a 10GbE module is a likely candidate for the  Gigabit Ethernet switch. The SPP does terminate VLANS, but does not perform VLAN switching.
    110119
    111 The SPP does terminate VLANS, but does not perform VLAN switching.  Initially, we plan that Internet2 will create multiple static VLAN connections with distinct tags between each pair of SPPs in the I2 core !PoPs (two SPPs are in Spiral 1). Typically, each adjacent pair of SPPs will be connected by 2 parallel links. PoP locations for GENI deployment are under discussion with I2.
     120Like normal PlanetLab nodes, SPPs use IP to tunnel packets between adjacent elements. While experimental
     121networks may define their own protocols and packet formats, every packet sent to/from an SPP must be
     122encapsulated in an IP packet. The port number in the IP header is used to determine which slice a packet
     123is associated with.
    112124
    113 To support some kinds of end-to-end non-IP experiments, virtual ethernets through regional networks to experimental data sources and sinks will also be needed.  These will be created incrementally in the spirals, as early experimenters join the integration teams.  The endpoints and regional networks are currently TBD, but some likely early candidates will come from other project sites in the PlanetLab control framework in Spiral 1.
     125We expect to provide additional VLAN-based "tail circuits" to regional networks (specifically GPENI and MAX).
     126These will connect to routers within the regional network providing a remote access point into the SPP network.
    114127
    115128== GPO Liaison System Engineer ==