1. LHCOPN / LHCONE Status Update John Shade /CERN IT-CS Summary of the LHCOPN/LHCONE meeting in Amsterdam Grid Deployment Board, October 2011

2. Quick update on Washington and Amsterdam LHCOPN/LHCONE meetings perfSONAR for monitoring LHCOPN is for T0 – T1 and T1 – T1 traffic LHCONE is a network to improve T1 – T2 – T3 connections (currently general-purpose IP network) LHCONE notes from D. Foster’s report to the WLCG Overview Board end September OB endorsed the strategy http://lhcone.net GDB update on LHCOPN/LHCONE meeting J.Shade Introduction 12-OCT-20112

3. perfSONAR-MDM service provided by DANTE was not being used by LHCOPN sites US-ATLAS has been working with perfSONAR- PS toolkit for several years Decision in Washington to deploy perfSONAR- PS in LHCOPN This was done within 3 months at all sites; new H/W being added Has already proved useful for debugging CERN-AGLT2 throughput problem For LHCONE, choice will be up to sites The two versions should be interoperable GDB update on LHCOPN/LHCONE meeting J.Shade 3 perfSONAR 12-OCT-2011

4. GDB update on LHCOPN/LHCONE meeting J.Shade BNL Dashboard 12-OCT-20114

5. GDB update on LHCOPN/LHCONE meeting J.Shade 5 IN2P3 Throughput Tests 12-OCT-2011

6. GDB update on LHCOPN/LHCONE meeting J.Shade 6 What of Sander’s dashboard? 12-OCT-2011

7. Great job done by all sites to get initial implementation of perfSONAR-PS working !! Now we need to fine-tune and achieve steady- state operations perfSONAR-MDM will be phased-out in LHCOPN (only) Working with developers to improve security of web-sites and to use grid certificates! Working on having identical hardware and two dedicated servers at each site. GDB update on LHCOPN/LHCONE meeting J.Shade Today’s Status 12-OCT-20117

8. Twiki: https://twiki.cern.ch/twiki/bin/view/LHCOPN/PerfsonarPS https://twiki.cern.ch/twiki/bin/view/LHCOPN/PerfsonarPS perfSONAR Toolkit Page: http://psps.perfsonar.net/toolkit/http://psps.perfsonar.net/toolkit/ Tom Wlodek’s Dashboard: https://perfsonar.usatlas.bnl.gov:8443/exda/?page=25&cloudName=LHCOPN https://perfsonar.usatlas.bnl.gov:8443/exda/?page=25&cloudName=LHCOPN DESY WLCG workshop presentations: https://indico.desy.de/conferenceOtherViews.py?view=standard&confId=4019 https://indico.desy.de/conferenceOtherViews.py?view=standard&confId=4019 GDB update on LHCOPN/LHCONE meeting J.Shade 8 References 12-OCT-2011

9. Coordinated through the LHCOPN community All the large R&E providers are represented. The LHC user communities are invited. But this (unlike the LHCOPN) is not a CERN-led activity. GDB update on LHCOPN/LHCONE meeting J.Shade 9 LHCONE 12-OCT-2011

10. Providing some ‘guarantees’ of performance Large data flows across managed bandwidth that would provide better determinism than shared IP networks. Segregation from competing traffic flows. Manage capacity as Number of sites x Max flow/site x Number of Flows increases. Better utilization of resources Use all available resources especially transatlantic. Provide better traffic management and engineering capability Leverage investments being made in advanced networking Access to more resources. GDB update on LHCOPN/LHCONE meeting J.Shade 10 The promise of LHCONE 12-OCT-2011

11. LHCONE is investigating different approaches for providing capability and managing large data flows. It is not yet a production service There is no clear agreement (yet) on the long-term, multi-domain, inter-continental technical solutions Prototype is being ‘financed’ by the network providers with the motivation of providing new types of services to the user communities. Utilising some additional research network capacity (transatlantic projects such as ACE) or national infrastructures (NREN’s, I2, ESNet). GDB update on LHCOPN/LHCONE meeting J.Shade 1112-OCT-2011

12. Intention was to execute a prototype proof of concept Based on the concept of Open Lightpath Exchanges. Switched core, routed edge. Recognize individual constraints Allow everyone to use existing equipment. Use existing standards. This has resulted in an interesting and working proto-infrastructure But scalability and manageability are doubtful with current technology. Slow down the move to a production infrastructure to investigate emerging solutions New standards for L2 networking. GDB update on LHCOPN/LHCONE meeting J.Shade 1212-OCT-2011

13. GDB update on LHCOPN/LHCONE meeting J.Shade 13 Detailed View (from Bill Johnson, ESNet) 12-OCT-2011

14. There is no imminent problem of saturating existing R&E IP networks and therefore constructing simply an independent IP network for large science communities, such as HEP has limited value. General purpose IP networks remain the main production facility for the LHC traffic until at least the LHC restart, 2015. All R&E network providers are investing in many initiatives (Dynes, DICE etc) to investigate the future of large science flows beyond traditional IP networks and should therefore work together on this global initiative. LHCONE should be the exemplar of that approach applicable to all future large-scale science experiments on a world wide scale. It should be ambitious in its approaches on the timeframe of the next 3 years. It should aim to bring an alternative to “traditional” large-scale IP infrastructures or demonstrate that it is not feasible, economic or advantageous to do so. The existing multi-VLAN infrastructure should continue to be used and developed but also evolved along the common lines to be decided by the architecture group with a view to manageability and integrating new approaches. Perhaps the scope needs to be limited in the short term. LHCONE should engage with early adopter user communities in a managed way to demonstrate that the new infrastructures can provide production services. This should bring new capability to the early adopters and not impact the current production capabilities. This should be coordinated, for the LHC, with the experiments. GDB update on LHCOPN/LHCONE meeting J.Shade 14 Views endorsed by Oversight Board 12-OCT-2011

15. WLCG, at the latest Overview Board, does not see an immediate problem from the "doing physics" point of view. Therefore, LHCONE is encouraged to lay solid foundations for long- term future. In the meantime, the current set up continues. Important to test and get experience/feedback on the implementation regarding global VLAN, spanning tree etc. GDB update on LHCOPN/LHCONE meeting J.Shade 15 Architecture Group 12-OCT-2011

16. Experiments need to be more involved in the coordination process Sites need to work through their experiments’ computing operations coordination contacts when attempting to connect to LHCONE One of the essential questions is, how do the stakeholders stay up-to-date as to progress and development regarding the LHCONE infrastructure as it evolves in the various regions of the world? GDB update on LHCOPN/LHCONE meeting J.Shade 16 Experiments 12-OCT-2011

17. GDB update on LHCOPN/LHCONE meeting J.Shade17