November 1 st 2010, Internet2 Fall Member Mee5ng Jason Zurawski Research Liaison

Transcription

1 November 1 st 2010, Internet2 Fall Member Mee5ng Jason Zurawski Research Liaison

2 Agenda DYNES (Eric/Jason) SC10 Ac5vi5es (All) LHCOPN Update (Jason) Other Hot Topics? 2 11/1/10, 2010 Internet2

3 DYNES Background Internet2 approached by 3 universi5es (Caltech, University of Michigan, Vanderbilt) and asked to lead a proposal on behalf of LHC and R&E community (July 2009) MRI- R2 solicita5on capped the per university submissions at 3 Issue was referred to advisory councils; recommenda5on to proceed from AOAC and RAC (July 2009) Internet2 convened a series of community calls (August 2009) With strong community support, submi]ed proposal to Major Research Instrument Recovery and Reinvestment (MRI- R2) (August 2009) Request was for ~$2 million Roughly 50% for equipment, 50% for personnel 3 11/1/10, 2010 Internet2

4 DYNES Summary What is it?: A na5onwide cyber- instrument spanning ~40 US universi5es and ~14 Internet2 connectors Extends Internet2 s ION service into regional networks and campuses, based on OSCARS implementa5on of IDC protocol (developed in partnership with ESnet) Who is it? A collabora5ve team including Internet2, Caltech, University of Michigan, and Vanderbilt University Community of regional networks and campuses LHC, astrophysics community, OSG, WLCG, other virtual organiza5ons What are the goals? Support large, long- distance scien5fic data flows in the LHC, other leading programs in data intensive science (such as LIGO, Virtual Observatory, and other large scale sky surveys), and the broader scien5fic community Build a distributed virtual instrument at sites of interest to the LHC but available to R&E community generally 4 11/1/10, 2010 Internet2

5 DYNES - Dynamic Network Circuits DYNES will deliver the needed capabili5es to the LHC, and to the broader scien5fic community at all the campuses served, by coupling to their analysis systems: Dynamic network circuit provisioning: IDC Controller Data transport: Low Cost IDC- capable Ethernet Switch; FDT Server for high throughput, Low cost storage array where needed (also non- LHC) End- to- end monitoring services DYNES does not fund more bandwidth, but provides access to Internet2 s dynamic circuit network ( ION ), plus the standard mechanisms, tools and equipment needed To build circuits with bandwidth guarantees across mul5ple network domains, across the U.S. and to Europe In a manageable way, with fair- sharing Will require scheduling services at some stage To build a community with high throughput capability using standardized, common methods

6 DYNES Update As of Summer, 2010, DYNES has been funded! Revised budget: ~$1.74 million Hardware budget unchanged Personnel budget reduced ~25% Success due to strong community support Going forward, we are looking for strong community engagement Need to adapt the plan in response to NSF requests and evolving network infrastructure h]p:// 6 11/1/10, 2010 Internet2

7 DYNES Community Support Internet2 received a total of 60 Le]ers of Collabora5on 44 Universi5es (some duplicates) 14 Regional Networks 1 Virtual Organiza5on 1 Federal Lab 7 11/1/10, 2010 Internet2

8 DYNES System Descrip5on AIM: extend hybrid & dynamic capabili5es to campus & regional networks. A DYNES instrument must provide two basic capabili5es at the Tier 2S, Tier3s and regional networks: 1. Network resource alloca5on such as bandwidth to ensure performance of the transfer 2. Monitoring of the network and data transfer performance All networks in the path require the ability to allocate network resources and monitor the transfer. This capability currently exists on backbone networks such as Internet2 and ESnet, but is not widespread at the campus and regional level. In addi5on Tier 2 & 3 sites require: 3. Hardware at the end sites capable of making op5mal use of the available network resources Two typical transfers that DYNES supports: one between a Tier 2 and a Tier 3 and another between a Tier 2 and a Tier 1 site. The clouds represent the network domains involved in such a transfer.

9 DYNES: Tier2 and Tier3 - Instrument Design Each DYNES (sub- )instrument at a Tier2 or Tier3 site consists of the following hardware, where each item has been carefully chosen to combine low cost & high performance: 1. An Inter- domain Controller (IDC) 2. An Ethernet switch 3. A Fast Data Transfer (FDT) server. Sites with 10GE throughput capability will have a dual- port Myricom 10GE network interface in the server. 4. An a]ached disk array with a Serial A]ached SCSI (SAS) controller capable of several hundred MBytes/ sec to local storage Gbps with 2 Controllers The Fast Data Transfer (FDT) server connects to the disk array via the SAS controller and runs FDT software developed by Caltech. FDT is an asynchronous multithreaded system that automatically adjusts I/O and network buffers to achieve maximum network utilization. The disk array stores datasets to be transferred among the sites in some cases. The FDT server serves as an aggregator/ throughput optimizer in this case, feeding smooth flows over the networks directly to the Tier2 or Tier3 clusters. The IDC server handles the allocation of network resources on the switch, inter-actions with other DYNES instruments related to network pro-visioning, and network performance monitoring. The IDC creates virtual LANs (VLANs) as needed.

10 DYNES: Regional Network - Instrument Design Regional networks require 1. An Ethernet switch 2. An Inter- domain Controller (IDC), as shown. The configura5on of the IDC consists of OSCARS, DRAGON, and perfsonar just as in the Tier2/ Tier 3 cases. This allows the regional network to provision resources on- demand through interac5on with the other instruments A regional network does not require a disk array or FDT server because they are providing transport for the Tier 2 and Tier 3 data transfers, not ini5a5ng them. 1 At the network level, each regional connects the incoming campus connection to the Ethernet switch provided. Optionally, if a regional network already has a qualified switch compatible with the dynamic software that they prefer, they may use that instead, or in addition to the provided equipment. The Ethernet switch provides a VLAN dynamically allocated by OSCARS & DRAGON. The VLAN has quality of service (QoS) parameters set to guarantee the bandwidth requirements of the connection as defined in the VLAN. These parameters are determined by the original circuit request from the researcher / application. through this VLAN, the regional provides transit between the campus IDCs connected in the same region or to the global IDC infrastructure. 2

11 DYNES Site Selec5on Process All sites will need to apply Applica5on process s5ll TBD Goal is to keep it lightweight, but fair External review panel Composi5on and process s5ll TBD Likely 6 members CMS overall representa5ve CMS Tier 3 representa5ve ATLAS overall representa5ve ATLAS Tier 3 representa5ve 2 Non- LHC high performance networking community reps Plus ex- officio members: PI and co- Pis Community feedback encouraged on site selec5on process 11 11/1/10, 2010 Internet2

12 DYNES Roadmap ICO and Council no5fica5on (Completed August 2010) Community announcement Le]er, website (Completed) 2 Community Calls (August 5 th and August 17 th ) Set up external review panel (October, 2010) CFP (October, 2010) Calls with individual regionals and with individual campuses (plus associated regional) upon request Ongoing in the Late Summer and Fall 2010 DYNES BoF (Nov 2010, at the Internet2 FMM in Atlanta) Site selec5ons announced (Late 2010) Distributed virtual Instrument building begins in /1/10, 2010 Internet2

13 Ques5ons Please send ques5ons to dynes- PI List: Eric Boyd (Internet2) Shawn McKee (University of Michigan) Harvey Newman (Caltech) Paul Sheldon (Vanderbilt) Project updates shared via and mailing list Subscrip5on informa5on found on the website 13 11/1/10, 2010 Internet2

14 SC10 DYNES Demonstra5on Caltech Booth (# 2713) Internet2 Booth (# 3539) Vanderbilt Booth (# 4341) External Sites (University of Michigan, CERN, BNL) Will feature an example of DYNES Hardware FDT Server Storage ION enabled switch/idc Server Use of the ION service for dynamic circuits, general IP connec5vity at SC /1/10, 2010 Internet2

15 SC10 Sample booth setup: 15 11/1/10, 2010 Internet2

16 LHCOPN Update Mee5ng held Oct 7 th - 8 CERN h]p://indico.cern.ch/conferencedisplay.py?confid= Interes5ng discussions: WLCG wants to work on a way to solve trouble 5ckets faster, and with more feedback for everyone in the process. MDM monitoring solu5on reliability is improving. Developing new Dashboards/Weathermaps (NL T1 leading effort w/ help from the Monitoring Working Group) Working Group forming to discuss changes to the LHCOPN model (incorpora5on of Tier2s) Report from Kors and Ian on usage pa]erns of LHC data Some surprises Data is some5mes used only once, and right a{er a collision So{ware tools in CMS are good about caching pulling data as needed. ATLAS tools rely on the data being available through the distribu5on model. May cause some changes Some sets are used more frequently than others Input from Kros/Ian will help the LHCT2 Working Group 16 11/1/10, 2010 Internet2

17 ? 17 11/1/10, 2010 Internet2

18 November 1 st 2010, Internet2 Fall Member Mee5ng Jason Zurawski Research Liaison For more informa5on, visit h]p:// /1/10, 2010 Internet2