Science &Research SIG

1. October 3rd 2912 Jason Zurawski – zurawski@internet2.eduSenior Research Engineer – Internet2 Office of the CTO Science &Research SIG

2. Research Support Center • Comprehensive end-to-end support for the research community • Work with the research community to understand their needs • Provide network engineering, planning and pricing for project and proposal development • Collaborate with the community to anticipate research needs • Foster network infrastructure and service research that can be incubated, tested and deployed

3. Research Support Center (cont) • Provide a clearinghouse for “researchers” who have questions regarding how to utilize Internet2 resources • Support extends to those who support researchers as well (e.g. sysadmin/netadmin at regional/campus nets). • Emphasis on cross domain needs – home for the homeless • Simple contact mechanisms • Email - rs@internet2.edu • Updated web presence – http://www.internet.edu/research

4. Dissecting the Research Support Center • Data as of 9/17/2012 • Total Tickets = 137 • 47 Open/In Progress • 90 Closed • Categories: • Network Performance = 36% • Increase from 25% since 7/2012 • GENI = 2% • Letters of Support = 21% • CC-NIE rush during Spring 2012 • Network Connectivity (Layer 2/General) = 7% • Research Support & Demo/Paper Collaboration = 15% • Internet2 Initiatives = 17% • Spike related to Internet2 NET+, Internet2 Innovation Platform, etc. • General = 2% • Other Tags: • 20% of tickets involve an international component • 9% are related to Healthcare/Medical topics • 7% (mostly in the performance space) are related to Internet2 NET+ activities zurawski@internet2.edu

5. Light At The End of the Performance Tunnel? • Is it daylight … or a train? • Specific performance concerns • End-to-end problems (campus to campus, Virtual Organizations, International links) • Application Fortitude • Instrumentation of Networks • Configuration of Tools • Training • Our Read: • We are seeing more reports • Less suffering in silence? More end-to-end work? Effective advertising? • Encouraging that people want to fix them, and that some are taking initiative in the community • Many campuses establishing “Research Engineer”, network-user interaction • VOs (SSERCA in Florida) pooling community computation and network resources. Serving as liaison between researchers and network providers (Campuses, FLR) zurawski@internet2.edu

6. Performance – Community XRoads • The Tools • The community has invested heavily in the perfSONAR framework. • One of many R&E success stories • The Deployments • Wide adoption (and use!) in all parts of the R&E community. • Emerging in the Commercial sector • The Use Cases • Keeping campus infrastructure available and highly capable • Directly supporting science • The Training • Measurement and monitoring are made easier with tools • Fixing the “hard problems” has a strong human aspect

7. Global Reach of perfSONAR Monitoring zurawski@internet2.edu

8. The Way Forward - Training • Approach Performance Training in some new ways • TTT: Restructure materials to encourage franchising to larger groups. • The knowledge will be passed down in a tree-like fashion • E1T1: One on one (or one to small number) explanation of the materials • Encourage recipients to pass along the knowledge

9. The Way Forward – Network Innovation • Architectural and procedural changes can have a big impact • E.g. Science DMZ • The scalability of traditional “TCP/IP” networks is being tested • Increasing number of users • Increasing number of use cases • The drive to do things better and more efficiently • New paradigms to consider • “Feedback” from the network • Intelligent switching and routing • Application based control • All working in harmony with the operational component

10. Shaking up the Application/Network Model • DYNES – NSF MRI Grant • Deliver hardware capable of advancing “Layer 2” networking deep into the campus and regional infrastructures • Encourage “Application Adoption” – particularly within scientific Vos • ~90% Deployed • New Twist – How to integrate SDN/OpenFlow ideas? • Testing new hardware/software currently • … Oh, and Monitoring is Necessary … • Reaching out to all participants to provide additional monitoring hardware zurawski@internet2.edu

11. Drinking from the Firehose Physics Large Hadron Collider (LHC) Life Sciences Magnetic Resonance Imager (MRI) Source: http://www.colinmcnulty.com Image by: CERN

12. Visualization Zen Physics LHC – Lead Ion Collision Life Sciences MRI – Monkey Brain Source: CERN (ALICE detector) Source: Van Wedeen, M.D., Martinos Center and Dept. of Radiology, Massachusetts General Hospital and Harvard University Medical School

13. The Facilities & Collaborators Physics 22 Particle Accelerators Life Sciences 758 Genome Sequencers Source: http://omicsmaps.com/, Dec. 5, 2011 Source: //find.mapmuse.com/map/particle-accelerators, Apr. 22, 2012

14. Beyond Moore’s Law

15. --Size, ++Data Mid - 2012 Illumina HiSeq 2500/1500 2013 Handheld USB Sequencer Image: Oxford Nanopore Technologies Source: http://www.illumina.com/systems/hiseq_systems/hiseq_2500_1500.ilmn

16. Preparedness • Some Campuses are creating a “Research Engineer” position explicitly • Interface with the researchers regularly • “Human networking” • Gauge needs (services, connectivity) • Translate into IT/NetEngrequirements • Escalate problems to other domains • Examples: • SSERCA • University of Colorado Boulder • The Pennsylvania State University

17. Disscusion • Who is doing what in the audience • What ways do you need help • From Internet2/Backbones • Regionals • Challenges? • CC-NIE – expectations • AOB

18. Science & Research SIG Jason Zurawski – zurawski@internet2.edu Senior Research Engineer, Internet2 Office of the CTO http://www.internet2.edu/research/