Changes between Version 3 and Version 4 of OverlayHostingNodes


Ignore:
Timestamp:
12/23/08 12:31:20 (12 years ago)
Author:
Jon Turner
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OverlayHostingNodes

    v3 v4  
    3535[milestone:"SPP: Architecture and Design Documentation (Draft)"][[BR]]
    3636[milestone:"SPP: Limited research available"][[BR]]
    37 [milestone:"SPP:Component Manager ICD"][[BR]]
     37[milestone:"SPP: Component Manager ICD"][[BR]]
    3838[milestone:"SPP: User Web Site"][[BR]]
    3939
     
    5252[[BR]]'''Spiral 1 Connectivity'''
    5353
    54 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 are not being developed to support the termination of VLAN tags, thus requiring a VLAN aware switch to connect to the SPP 1Gbps I/O. To view an SPP node configuration with connection requirements [http://groups.geni.net/geni/attachment/wiki/OverlayHostingNodes/SPP_gpoNodeConfig.pdf click here.]     
    55 
     54SPP 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
     55expect 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.]     
    5656
    5757''Size & Power Specifications''[[BR]]
     
    6666''IP addresses''
    6767
    68 Each SPP needs at least one public IP address, which is used by experimenters and others who want to access the SPP.    As usage expands, up to 3 additional addresses would be needed.  The virtual Ethernet interfaces do not use IP addresses.  There is also a need for at least one non-advertised IP address for each SPP for debugging, console, and other types of maintenance access.  Public addresses have been requested from Internet2.
     68Each SPP will connect to a local Internet 2 router, using multiple 1 GbE connections.
     69The number of such connections per site will vary from 2 to 4.
     70Each will need an I2 IP address for each such interfaces. These addresses should be advertised to I2-connected
     71universities, but need not be advertised to the public Internet.
     72Each SPP will also require a separate connection from its control processor. This can be a low bandwidth (10/100 Mb/s)
     73connection, and should be accessible from any I2-connected university. Public addresses have been requested from Internet2.
    6974
    7075IP connectivity between the PlanetLab clearinghouse and the SPP nodes is required.
     
    7479Layer 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.   
    7580
    76 Although the SPP does not terminate VLANS, it is VLAN-aware (can identify tags for example), and should eventually be able to manipulate VLANs as part of the PlanetLab control framework.  Initially, we plan that Internet2 will create static virtual Ethernets with distinct tags between each pair of SPPs in the I2 core !PoPs (two SPPs are in Spiral 1). PoP locations for GENI deployment are under discussion with I2.
     81The 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.
    7782
    78 To support some kinds of end-to-end non-IP experiments, virtual ethernets through regional networks to experiment 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.
     83To 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.
    7984
    8085'''GPO Liason System Engineer'''