Presentation of the LHCONE Architecture document Marco Marletta, GARR LHCONE Meeting Paris, Tuesday 5th April 2011 connect • communicate • collaborate
Agenda Background Design Definitions Architecture Services Policy Next steps connect • communicate • collaborate 2
Background 2004/2005 the LHC Optical Private Network (LHCOPN) was designed by experts and managers from the HEP- and (N)REN-communities. The experiments’ networking requirements are changed since then CERN took the initiative to ask the community for ideas at the October 2010 LHCOPN Meeting in Geneva. A small group of experts was tasked to take this outcome to a next level, and prepare a document for discussion A first architectural document was submitted at the LHCOPN Meeting in Lyon, France on February 10 and 11, 2011 and refined in later discussions We are now at version 2.2 connect • communicate • collaborate 3
The architecture document philosophy The architecture document is A high level architectural description of LHCONE Intended to enable different approaches in different continents / regions Not intended to be prescriptive; each continent / region will have to figure out how to implement access to LHCONE Not intended to be a complete description of LHCONE and environment, just LHCONE, at a high level connect • communicate • collaborate 4
High level design considerations A full mesh of data exchange paths is necessary “Unstructured” T2 traffic will be the norm in the future and is already showing up in significant ways on the global R&E network infrastructures A federated solution is the only feasible solution, given the range of: Scale (100+ sites) Geographical distribution (Only Antarctica is not involved) Diversity of the sites (1G to 10G to ?) Funding mechanisms The solution must allow for a smooth transition of user sites from general purpose routed networks to the purpose-built network It must not preclude the use of general purpose networks if it is chosen to do so connect • communicate • collaborate 5
Detailed design considerations (aka the 9 commandments) 1/2 1. LHCONE complements the LHCOPN by addressing a different set of data flows. LHCONE is physically and operationally distinct from LHCOPN. In future might use some common operational components (ex. TTS) 2. LHCONE enables high-volume data transport between T1s, T2s, and T3s. T2s and T3s will be able to exchange data with any T1 or T2 or T3 and viceversa Reflects the “unstructured” traffic flow trends 3. LHCONE separates LHC-related large flows from the general purpose routed infrastructures of R&E networks. separation possible through distinct infrastructure and/or traffic engineering 4. LHCONE incorporates all viable national, regional and intercontinental ways of interconnecting Tier1s, Tier2s, and Tier 3s. inclusive of technologies and methods for interconnection in use connect • communicate • collaborate 6
Detailed design considerations (aka the 9 commandments) 2/2 5. LHCONE uses an open and resilient architecture that works on a global scale. T2s and T3s should be able to join when they are ready, using their favourite connection method The core of the LHCONE is built as a resilient infrastructure 6. LHCONE provides a secure environment for T1-T2, T2-T2, and T2-T3 data transport. The infrastructure provides for private connectivity among the connectors 7. LHCONE provides connectivity directly to T1s, T2s, and T3s, and to various aggregation networks (European NRENs, GÉANT, and North American RONs, Internet2, ESnet, CANARIE, etc., that may provide the direct connections to the T1s, T2s, and T3s. 8. LHCONE is designed for agility and expandability. accommodating for rising data volumes adaption to new networking technologies prepared to accommodate changes in data models of the LHC experiments The LHCONE components themselves may evolve The sites connecting to LHCONE may evolve over time 9. LHCONE allows for coordinating and optimizing transoceanic data flows, ensuring the optimal use of transoceanic links using multiple providers by the LHC community. connect • communicate • collaborate 7
Definitions Tier 1s, Tier 2s and Tier 3s are collectively referred to as “ T1/2/3 .” aggregation networks Any network that provides connections to T1/2/3s, and then in turn connects to LHCONE connector Any entity that can connect to LHCONE: T1/2/3 and aggregation networks exchange point hardware and physical facilities that provide the access points for LHCONE and the interconnect fabric of LHCONE distributed exchange point a geographically distributed collection of network nodes under a single administrative authority, which to a connector appear as one single unit, administratively and operationally. connect • communicate • collaborate 8
Architecture LHCONE builds on the hybrid network infrastructures and open exchange points provided today by the major Research and Education networks worldwide Building blocks Single node exchange points Continental / regional distributed exchange points Interconnect circuits between exchange points Access methods fixed lightpath layer3 connectivity dynamic circuit dynamic circuit with guaranteed bandwidth We envisage that many of the Tier1/2/3s may connect to LHCONE through aggregation networks connect • communicate • collaborate 9
LHCONE Example Implementation TX TX TX TX TX TX TX TX TX Aggregation Aggregation Network Network Aggregation Aggregation Network Network continent continent continent LHCONE distributed exchange point single node exchange point connect • communicate • collaborate 10
Services offered in LHCONE Shared Layer 2 domains (private VLAN broadcast domains) LHCONE provides IPv4 and IPv6 addresses on shared layer 2 domains that include all connectors. Layer 3 routing is up to the connectors (using BGP, public IP addresses and public AS numbers) A Route Server per continent is planned to be available in order to speedup the initial exchange of traffic when new connectors emerge Point-to-point layer 2 connections VLANS without bandwidth guarantees can be set up between pairs of connectors Lightpath / dynamic circuits with bandwidth guarantees Lightpaths can be set up between pairs of connectors subject to a resource allocation policy agreed on by the community. Each Tier1/2/3 and each aggregation network is encouraged to install a perfSONAR node for both measurement and testing. LHCONE does not preclude the continued use of the general R&E network infrastructure by the Tier1/2/3s, as is done today. connect • communicate • collaborate 11
Policy Any Tier1/2/3 can connect to LHCONE through one or more aggregation networks, and/or exchange points. Within LHCONE, transit is provided from any Tier1/2/3 connected to the LHCONE to any other Tier1/2/3s connected to the LHCONE. Exchange points and distributed exchange points must carry all LHC traffic offered to them (and only LHC traffic), and be built in carrier- neutral facilities so that any connector can connect with their own fiber or using circuits provided by any telecom provider. No additional restrictions can be imposed on LHCONE by the LHCONE component contributors. The policies for Tier1/2/3s to connect to aggregation networks are outside the scope of the architecture document. The aggregator networks and/or the Tier1/2/3s might impose additional policy constraints on their own connections. connect • communicate • collaborate 12
Next steps Identify an european prototype team to reach consensus on the implementation DFN/GARR/RENATER asked DANTE to convene the team Submit a prototype plan to the LHCT2S group for approval Implement the prototype (proof of concept) Addressing some short term goals – Evaluate the effectiveness of the architecture – Demonstrate the value of the architecture to funding agencies – Addressing some short term needs of the experiments Built using existing resources in the R&E community Evaluate actions to be taken beyond the prototype More permanent components Refine governance model Refine architecture, services, policies connect • communicate • collaborate 13
THANK YOU connect • communicate • collaborate
Recommend
More recommend
