Changes between Version 1 and Version 2 of clusterdvlan
- Timestamp:
- 10/28/09 15:12:42 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
clusterdvlan
v1 v2 1 [[Page Outline]] 2 1 3 = GENI Cluster D Spiral 2 Connectivity Plan = 2 4 3 Goals 5 == Goals == 6 4 7 The following goals have been identified for the GNEI Cluster D Spiral 2 connectivity plan: 5 8 6 a) Cluster D entities (aggregates and the clearinghouse) need reliable, high-bandwidth L3 (IP) and L2 (VLAN) connectivity between each other to meet their experimentation goals for Spiral 2.9 a) Cluster D entities (aggregates and the clearinghouse) need reliable, high-bandwidth L3 (IP) and L2 (VLAN) connectivity between each other to meet their experimentation goals for Spiral 2. 7 10 8 b) L3 will be used to reach publically-available services via public IP addresses and /or DNS names.11 b) L3 will be used to reach publically-available services via public IP addresses and /or DNS names. 9 12 10 c) L2 (VLAN) connectivity will be used to join aggregate (and possibly other) resources via pt-to-pt or multi-point VLANs.13 c) L2 (VLAN) connectivity will be used to join aggregate (and possibly other) resources via pt-to-pt or multi-point VLANs. 11 14 12 d) Pt-to-pt or multi-point VLANs will be used between entities involved in an experiment, where each entity is assigned a unique private IP addresses for the duration of the experiment. This has proven to be a very useful and convenient way to group entities for an experiment, e.g., the OMF network arrangement.15 d) Pt-to-pt or multi-point VLANs will be used between entities involved in an experiment, where each entity is assigned a unique private IP addresses for the duration of the experiment. This has proven to be a very useful and convenient way to group entities for an experiment, e.g., the OMF network arrangement. 13 16 14 e) Pt-to-pt or multi-point VLANs may be used between entities involved in an experiment, where each entity utilizes a L3 protocol that is not IP.17 e) Pt-to-pt or multi-point VLANs may be used between entities involved in an experiment, where each entity utilizes a L3 protocol that is not IP. 15 18 16 f) Two backbone network have donated resources to GENI for Spiral 2, and these will be utilized to provide reliable, high-bandwidth L3 and L2 connectivity: Internet2 and NLR. See http://groups.geni.net/geni/wiki/GeniInternet2 and http://groups.geni.net/geni/wiki/GeniNationalLambdaRail19 f) Two backbone network have donated resources to GENI for Spiral 2, and these will be utilized to provide reliable, high-bandwidth L3 and L2 connectivity: Internet2 and NLR. See http://groups.geni.net/geni/wiki/GeniInternet2 and http://groups.geni.net/geni/wiki/GeniNationalLambdaRail 17 20 18 g) Each Cluster D entity (aggregate or clearinghouse) must reach Internet2 and/or NLR to get L3 and L2 connectivity. It is expected that this will include connections through a campus network and a regional network to Internet2 or NLR (but not typically both).21 g) Each Cluster D entity (aggregate or clearinghouse) must reach Internet2 and/or NLR to get L3 and L2 connectivity. It is expected that this will include connections through a campus network and a regional network to Internet2 or NLR (but not typically both). 19 22 20 h) It is important that all Cluster D entities have L3 and L2 connectivity with each other in Spiral 2; if not, then the combinations of joint experiment would be limited. This implies connectivity is needed between Internet2 and NLR, which is not currently supported.23 h) It is important that all Cluster D entities have L3 and L2 connectivity with each other in Spiral 2; if not, then the combinations of joint experiment would be limited. This implies connectivity is needed between Internet2 and NLR, which is not currently supported. 21 24 22 i) It is important that the complexities of providing the connectivity be hidden from the experimenter, who should be able to request a L3 (IP) or L2 (VLAN) connection by dealing with primarily their own entity.25 i) It is important that the complexities of providing the connectivity be hidden from the experimenter, who should be able to request a L3 (IP) or L2 (VLAN) connection by dealing with primarily their own entity. 23 26 24 j) It should be possible to extend the Cluster D connectivity plan to include resources in the other GENI clusters, with the eventual goal of reliable, high-bandwidth L3 (IP) and L2 (VLAN) connectivity between all GENI entities.27 j) It should be possible to extend the Cluster D connectivity plan to include resources in the other GENI clusters, with the eventual goal of reliable, high-bandwidth L3 (IP) and L2 (VLAN) connectivity between all GENI entities. 25 28 26 k) The resulting connectivity plan should support this roadmap for Cluster D VLAN capabilities:29 k) The resulting connectivity plan should support this roadmap for Cluster D VLAN capabilities: 27 30 28 31