The Science DMZ: A Network Design Pa8ern for Data- Intensive Science

Transcription

1 The Science DMZ: A Network Design Pa8ern for Data- Intensive Science Jason Zurawski zurawski@es.net Science Engagement Engineer, ESnet Lawrence Berkeley National Laboratory KINBER Webinar March 4 th 2015

2 Overview ESnet Overview Science DMZ MoIvaIon and IntroducIon Science DMZ Architecture Network Monitoring Data Transfer Nodes & ApplicaIons Science DMZ Security User Engagement Wrap Up 2 ESnet Science Engagement (engage@es.net) - 3/3/15

3 SC Supports Research at More than 300 Institutions Across the U.S ESnet at a Glance High- speed naional network, opimized for DOE science missions: connecing 40 labs, plants and faciliies with >100 networks (naional and internaional) $32.6M in FY14, 42FTE older than commercial Internet, growing twice as fast $62M ARRA in 2009/2010 grant for 100G upgrade: Universities DOE laboratories transiion to new era of opical networking world s first 100G network at coninental scale The Office of Science supports: 27,000 Ph.D.s, graduate students, undergraduates, engineers, and technicians 26,000 users of open-access facilities 300 leading academic institutions 17 DOE laboratories 8 Culture of urgency: 4 awards in past 3 years R&D100 Award in FY13 5 out of 5 for customer saisfacion in last review Dedicated staff to support the mission of science 3 ESnet Science Engagement (engage@es.net) - 3/3/15

4 Network as Infrastructure Instrument ESnet Vision: ScienIfic progress will be completely unconstrained by the physical locaion of instruments, people, computaional resources, or data. 4 ESnet Science Engagement (engage@es.net) - 3/3/ , Energy Sciences Network

5 Overview ESnet Overview Science DMZ MoIvaIon and IntroducIon Science DMZ Architecture Network Monitoring Data Transfer Nodes & ApplicaIons Science DMZ Security User Engagement Wrap Up 5 ESnet Science Engagement (engage@es.net) - 3/3/15

6 Mo8va8on Science & Researcher are everywhere Size of school/endowment does not ma8er there is a researcher at your facility right now that is a8emping to use the network for a research acivity Networks are an essenial part of data- intensive science Connect data sources to data analysis Connect collaborators to each other Enable machine- consumable interfaces to data and analysis resources (e.g. portals), automaion, scale Performance is criical ExponenIal data growth Constant human factors (Imelines for analysis, remote users) Data movement and analysis must keep up EffecIve use of wide area (long- haul) networks by scienists has historically been difficult (the Wizard Gap ) 6 ESnet Science Engagement (engage@es.net) - 3/3/15

7 Tradi8onal Big Science 7 ESnet Science Engagement (engage@es.net) - 3/3/15

8 Big Science Now Comes in Small Packages and is happening on your campus. Guaranteed. 8 ESnet Science Engagement (engage@es.net) - 3/3/15

9 Understanding Data Trends 100PB 10PB 1PB Small collaboration scale, e.g. light and neutron sources Medium collaboration scale, e.g. HPC codes A few large collaborations have internal software and networking organizations Data Scale 100TB 10TB Large collaboration scale, e.g. LHC 1TB 100GB 10GB Collaboration Scale 9 ESnet Science Engagement (engage@es.net) - 3/3/15

10 Data Mobility in a Given Time Interval (Theore8cal) These tables available: 10 ESnet Science Engagement (engage@es.net) - 3/3/15

11 The Central Role of the Network The very structure of modern science assumes science networks exist: high performance, feature rich, global scope What is The Network anyway? The Network is the set of devices and applicaions involved in the use of a remote resource This is not about supercomputer interconnects This is about data flow from experiment to analysis, between faciliies, etc. User interfaces for The Network portal, data transfer tool, workflow engine Therefore, servers and applicaions must also be considered What is important? Ordered list: 1. Correctness 2. Consistency 3. Performance 11 ESnet Science Engagement (engage@es.net) - 3/3/15

12 TCP Ubiquitous and Fragile Networks provide connecivity between hosts how do hosts see the network? From an applicaion s perspecive, the interface to the other end is a socket CommunicaIon is between applicaions mostly over TCP TCP the fragile workhorse TCP is (for very good reasons) Imid packet loss is interpreted as congesion Packet loss in conjuncion with latency is a performance killer We can address the first, science hasn t fixed the 2 nd (yet) Like it or not, TCP is used for the vast majority of data transfer applicaions (more than 95% of ESnet traffic is TCP) 12 ESnet Science Engagement (engage@es.net) - 3/3/15

13 A small amount of packet loss makes a huge difference in TCP performance Local (LAN) With loss, high performance beyond metro distances is essentially impossible InternaIonal Metro Area Regional ConInental Measured (TCP Reno) Measured (HTCP) Theoretical (TCP Reno) Measured (no loss) 13 ESnet Science Engagement (engage@es.net) - 3/3/15

14 Lets Talk Performance "In any large system, there is always something broken. Jon Postel Modern networks are occasionally designed to be one- size- fits- most e.g. if you have ever heard the phrase converged network, the design is to facilitate CIA (ConfidenIality, Integrity, Availability) This is not bad for protecing the HVAC system from hackers. Causes of fricion/packet loss: Small buffers on the network gear and hosts Incorrect applicaion choice Packet disrupion caused by overzealous security CongesIon from herds of mice It all starts with knowing your users, and knowing your network 14 ESnet Science Engagement - 3/3/15

15 PuPng A Solu8on Together EffecIve support for TCP- based data transfer Design for correct, consistent, high- performance operaion Design for ease of troubleshooing Easy adopion (for all stakeholders) is criical Large laboratories and universiies have extensive IT deployments Small universiies/faciliies have overworked/understaffed IT departments DrasIc change is prohibiively difficult Cybersecurity defensible without compromising performance Borrow ideas from tradiional network security TradiIonal DMZ Separate enclave at network perimeter ( Demilitarized Zone ) Specific locaion for external- facing services Clean separaion from internal network Do the same thing for science Science DMZ 15 ESnet Science Engagement (engage@es.net) - 3/3/15

16 The Science DMZ Superfecta Engagement Partnerships EducaIon & ConsulIng Resources & Knowledgebase Engagement with Network Users Data Transfer Node High performance Configured for data transfer Proper tools Dedicated Systems for Data Transfer Performance TesIng & Measurement perfsonar Enables fault isolaion Verify correct operaion Widely deployed in ESnet and other networks, as well as sites and faciliies Network Architecture Science DMZ Dedicated locaion for DTN Proper security Easy to deploy - no need to redesign the whole network 16 ESnet Science Engagement (engage@es.net) - 3/3/15

17 Overview ESnet Overview Science DMZ MoIvaIon and IntroducIon Science DMZ Architecture Network Monitoring Data Transfer Nodes & ApplicaIons Science DMZ Security User Engagement Wrap Up 17 ESnet Science Engagement - 3/3/15

18 Abstract Deployment Simplest approach : add- on to exising network infrastructure All that is required is a port on the border router Small footprint, pre- producion commitment Easy to experiment with components and technologies DTN prototyping perfsonar tesing Limited scope makes security policy excepions easy Only allow traffic from partners (use ACLs) Add- on to producion infrastructure lower risk IdenIfy applicaions that are running (e.g. the DTN is not a general purpose machine it does data transfer, and data transfer only) Start with a single user/user case. If it works for them in a pilot, you can expand 18 ESnet Science Engagement (engage@es.net) - 3/3/15

19 Local And Wide Area Data Flows Border Router perfsonar Enterprise Border Router/Firewall WAN 10G 10GE perfsonar Clean, High-bandwidth WAN path 10GE Site / Campus access to Science DMZ resources Science DMZ Switch/Router 10GE Site / Campus LAN 10GE High performance Data Transfer Node with high-speed storage Per-service security policy control points perfsonar High Latency WAN Path Low Latency LAN Path 19 ESnet Science Engagement (engage@es.net) - 3/3/15

20 Non- R1 Campus This paradigm is not just for the big guys there is a lot of value for smaller insituions with a smaller number of users Can be constructed with exising hardware, or small addiions Does not need to be 100G, or even 10G. Capacity doesn t ma8er we want to eliminate fricion and packet loss The best way to do this is to isolate the important traffic from the enterprise Can be scoped to either the expected data volume of the science, or the availability of external facing resources (e.g. if the pipe to KINBER/3ROX/ MAGPI is small you don t want a single user monopolizing it) Factors: Are you comfortable with Layer 2 Networking? How rich is your cable/fiber plant? Can you create a dedicated facility for science? 20 ESnet Science Engagement (engage@es.net) - 3/3/15

21 Non- R1 Campus Fiber Rich Environment 21 ESnet Science Engagement - 3/3/15

22 Non- R1 Campus Layer 2 Switching 22 ESnet Science Engagement (engage@es.net) - 3/3/15

23 Non- R1 Campus Single Facility 23 ESnet Science Engagement - 3/3/15

24 Non- R1 Campus Every campus will be different If you are not fiber rich, other choices may be needed. If the researchers don t want to move to a dedicated facility, your opions are also limited Have discussions lay out what is possible and what is not ROI Statements: Eliminate congesion where you can the network path for the science user does not traverse the core - > be8er performance for her, and everyone else Improve the process of science the next Ime they go for an NSF/DOE/ NIST grant, they can say (with confidence) the network does what they need it to do Encourage others that are suffering in silence to seek you out. Once you have a success story, there will be others asking about it. 24 ESnet Science Engagement (engage@es.net) - 3/3/15

25 Overview ESnet Overview Science DMZ MoIvaIon and IntroducIon Science DMZ Architecture Network Monitoring Data Transfer Nodes & ApplicaIons Science DMZ Security User Engagement Wrap Up 25 ESnet Science Engagement - 3/3/15

26 Performance Monitoring Everything may funcion perfectly when it is deployed Eventually something is going to break Networks and systems are complex Bugs, mistakes, SomeImes things just break this is why we buy support contracts Must be able to find and fix problems when they occur (even if they have been that way for a long Ime) Must be able to find problems in other networks (your network may be fine, but someone else s problem can impact your users) TCP was intenionally designed to hide all transmission errors from the user: As long as the TCPs coninue to funcion properly and the internet system does not become completely pariioned, no transmission errors will affect the users. (From RFC793, 1981) 26 ESnet Science Engagement (engage@es.net) - 3/3/15

27 SoV Network Failures Hidden Problems Hard failures are well- understood Link down, system crash, sowware crash TradiIonal network/system monitoring tools designed to quickly find hard failures Sow failures result in degraded capability ConnecIvity exists Performance impacted Typically something in the path is funcioning, but not well Sow failures are hard to detect with tradiional methods No obvious single event SomeImes no indicaion at all of any errors Independent tesing is the only way to reliably find sow failures 27 ESnet Science Engagement - 3/3/15

28 Sample SoV Failures Rebooted router with full route table normal performance Gradual failure of optical line card Gb/s degrading performance repair one month 28 ESnet Science Engagement - 3/3/15

29 Tes8ng Infrastructure perfsonar perfsonar is: A widely- deployed test and measurement infrastructure ESnet, Internet2, US regional networks, internaional networks Laboratories, supercomputer centers, universiies A suite of test and measurement tools A collaboraion that builds and maintains the toolkit By installing perfsonar, a site can leverage over 1300 test servers deployed around the world perfsonar is ideal for finding sow failures Alert to existence of problems Fault isolaion VerificaIon of correct operaion Open Source, widely supported by a number of stakeholder organizaions 29 ESnet Science Engagement (engage@es.net) - 3/3/15

30 Lookup Service Directory Search: hyp://stats.es.net/servicesdirectory/ 30 ESnet Science Engagement - 3/3/15

31 perfsonar Dashboard: hyp://ps- dashboard.es.net 31 ESnet Science Engagement - 3/3/15

32 Overview ESnet Overview Science DMZ MoIvaIon and IntroducIon Science DMZ Architecture Network Monitoring Data Transfer Nodes & ApplicaIons Science DMZ Security User Engagement Wrap Up 32 ESnet Science Engagement - 3/3/15

33 Dedicated Systems Data Transfer Node The DTN is dedicated to data transfer Set up specifically for high- performance data movement System internals (BIOS, firmware, interrupts, etc.) Network stack Storage (global filesystem, Fibrechannel, local RAID, etc.) High performance tools No extraneous sowware LimitaIon of scope and funcion is powerful No conflicts with configuraion for other tasks Small applicaion set makes cybersecurity easier 33 ESnet Science Engagement - 3/3/15

34 Data Transfer Tool Comparison In addiion to the network, using the right data transfer tool is criical Data transfer test from Berkeley, CA to Argonne, IL (near Chicago). RTT = 53 ms, network capacity = 10Gbps. Tool Throughput scp: 140 Mbps HPN patched scp: 1.2 Gbps wp 1.4 Gbps GridFTP, 4 streams 5.4 Gbps GridFTP, 8 streams 6.6 Gbps Note that to get more than 1 Gbps (125 MB/s) disk to disk requires properly engineered storage (RAID, parallel filesystem, etc.) 34 ESnet Science Engagement (engage@es.net) - 3/3/15

35 Overview ESnet Overview Science DMZ MoIvaIon and IntroducIon Science DMZ Architecture Network Monitoring Data Transfer Nodes & ApplicaIons Science DMZ Security User Engagement Wrap Up 35 ESnet Science Engagement - 3/3/15

36 Science DMZ Security Goal disentangle security policy and enforcement for science flows from security for business systems RaIonale Science data traffic is simple from a security perspecive Narrow applicaion set on Science DMZ Data transfer, data streaming packages No printers, document readers, web browsers, building control systems, financial databases, staff desktops, etc. Security controls that are typically implemented to protect business resources owen cause performance problems SeparaIon allows each to be opimized 36 ESnet Science Engagement (engage@es.net) - 3/3/15

37 Performance Is A Core Requirement Core informaion security principles ConfidenIality, Integrity, Availability (CIA) Owen, CIA and risk miigaion result in poor performance In data- intensive science, performance is an addiional core mission requirement: CIA à PICA CIA principles are important, but if performance is compromised the science mission fails Not about how much security you have, but how the security is implemented Need a way to appropriately secure systems without performance compromises CollaboraIon Within The OrganizaIon All paries (users, operators, security, administraion) needs to sign off up this idea revoluionary vs. evoluionary change. Make sure everyone understands the ROI potenial. 37 ESnet Science Engagement (engage@es.net) - 3/3/15

38 Security Without Firewalls Data intensive science traffic interacts poorly with firewalls Does this mean we ignore security? NO! We must protect our systems We just need to find a way to do security that does not prevent us from geyng the science done Key point security policies and mechanisms that protect the Science DMZ should be implemented so that they do not compromise performance Traffic permi8ed by policy should not experience performance impact as a result of the applicaion of policy 38 ESnet Science Engagement (engage@es.net) - 3/3/15

39 Firewall Performance Example Observed performance, via perfsonar, through a firewall: Almost 20 Imes slower through the firewall Observed performance, via perfsonar, bypassing firewall: Huge improvement without the firewall 39 ESnet Science Engagement (engage@es.net) - 3/3/15

40 Overview ESnet Overview Science DMZ MoIvaIon and IntroducIon Science DMZ Architecture Network Monitoring Data Transfer Nodes & ApplicaIons Science DMZ Security User Engagement Wrap Up 40 ESnet Science Engagement - 3/3/15

41 Challenges to Network Adop8on Causes of performance issues are complicated for users. Lack of communicaion and collaboraion between the CIO s office and researchers on campus. Lack of IT experise within a science collaboraion or experimental facility User s performance expectaions are low ( The network is too slow, I tried it and it didn t work ). Cultural change is hard ( we ve always shipped disks! ). ScienIsts want to do science not IT support The Capability Gap 41 ESnet Science Engagement (engage@es.net) - 3/3/15

42 Bridging the Gap ImplemenIng technology is easy in the grand scheme of assising with science AdopIon of technology is different Does your cosmologist care what SDN is? Does your cosmologist want to get data from Chile each night so that they can start the next day without having to struggle with the tyranny of ineffecive data movement strategies that involve airplanes and white/brown trucks? 42 ESnet Science Engagement - 3/3/15

43 The Golden Spike We don t want ScienIsts to have to build their own networks Engineers don t have to understand what a tokomak accomplishes MeeIng in the middle is the process of science engagement: Engineering staff learning enough about the process of science to be helpful in how to adopt technology Science staff having an open mind to be8er use what is out there 43 ESnet Science Engagement (engage@es.net) - 3/3/ , Energy Sciences Network

44 Establishing Requirements h8p:// requirements/network- requirements- reviews/ The purpose of these reviews is to accurately characterize the near- term, medium- term and long- term network requirements of the science conducted by each program office. The reviews a8empt to bring about a network- centric understanding of the science process used by the researchers and scienists, to derive network requirements. We have found this to be an effecive method for determining network requirements for ESnet's customer base. 44 ESnet Science Engagement (engage@es.net) - 3/3/15

45 Overview ESnet Overview Science DMZ MoIvaIon and IntroducIon Science DMZ Architecture Network Monitoring Data Transfer Nodes & ApplicaIons On the Topic of Security User Engagement Wrap Up 45 ESnet Science Engagement - 3/3/15

46 Why Build A Science DMZ Though? What we know about scienific network use: Machine size decreasing, accuracy increasing HPC resources more widely available and potenially distributed from where the scienists are WAN networking speeds now at 100G, MAN approaching, LAN as well Value ProposiIon: If scienists can t use the network to the fullest potenial due to local policy constraints or bo8lenecks they will find a way to get their done outside of what is available. Without a Science DMZ, this stuff is all hard No one will use it. Maybe today, what about tomorrow? We don t have these demands currently. Next gen technology is always a day away 46 ESnet Science Engagement (engage@es.net) - 3/3/15

47 Wrapup The Science DMZ design pa8ern provides a flexible model for supporing high- performance data transfers and workflows Key elements: AccommodaIon of TCP Sufficient bandwidth to avoid congesion Loss- free IP service LocaIon near the site perimeter if possible Test and measurement Dedicated systems Appropriate security Support for advanced capabiliies (e.g. SDN) is much easier with a Science DMZ 47 ESnet Science Engagement (engage@es.net) - 3/3/15

48 The Science DMZ in 1 Slide Consists of four key components, all required: FricIon free network path Highly capable network devices (wire- speed, deep queues) Virtual circuit connecivity opion Security policy and enforcement specific to science workflows Located at or near site perimeter if possible Dedicated, high- performance Data Transfer Nodes (DTNs) Hardware, operaing system, libraries all opimized for transfer Includes opimized data transfer tools such as Globus Online and GridFTP Performance measurement/test node perfsonar Engagement with end users Details at h8p://fasterdata.es.net/science- dmz/ 2013 Wikipedia 48 ESnet Science Engagement (engage@es.net) - 3/3/15

49 Links ESnet fasterdata knowledge base h8p://fasterdata.es.net/ Science DMZ paper h8p:// final.pdf Science DMZ list Send mail to with the subject "subscribe esnet- sciencedmz Fasterdata Events (Workshop, Webinar, etc. announcements) Send mail to with the subject "subscribe esnet- fasterdata- events perfsonar h8p://fasterdata.es.net/performance- tesing/perfsonar/ h8p:// 49 ESnet Science Engagement - 3/3/15

50 Ask us anything: Preparing for CC- DNI Deploying perfsonar Debugging a problem A8ending a training event Designing a network 50 ESnet Science Engagement (engage@es.net) - 3/3/15

51 Thanks! Jason Zurawski Science Engagement Engineer, ESnet Lawrence Berkeley National Laboratory KINBER Webinar March 4 th 2015