Not Just Fast Data: �ESnet Networking Services to Enable Science
Jon-Paul Herron
Dale W. Carder
Ed Balas
Bruce Mah
John MacAuley
Overview of ESnet Advanced Services
Jon-Paul Herron
Department Head, ESnet Network Services
ESnet’s Service Philosophy: What Really Matters
3
ESnet’s Service Approach
World Class Network Infrastructure:
Like a Lego factory, our reliable, high performance network is the basis for our services.
Science-focused Capabilities: Like Lego pieces, we build flexible services and capabilities using this reliable infrastructure.
Tailored Solutions:
Like Lego models, we co-design with science projects to put the pieces together to create just what’s needed to accelerate their science.
4
ESnet Infrastructure By the Numbers
5
AVAILABILITY
PERFORMANCE
REACH
Science-focused Capabilities
6
Physical Connectivity
IP Transit
L2 VPN (OSCARS)
L3 VPN
Route Hijack Monitoring
Blackhole Routing
Cloud Connect
DNS Hosting
IP Address Assignment
Timing Service
Automation
ESnet Service Menu
Co-designed
Solutions
7
1
3x
1x
Putting It All Together: Our Future Vision
8
Site C
Site B
Site A
Cloud
Auto
L2 mesh
High Touch
High Touch
perfSONAR
perfSONAR
Measurement
Operations
Documentation
API/UI
Talks to Come
ESnet Cloud Services
Dale W. Carder
ESnet Network Engineering
ESnet-Enabled Public Cloud Examples
10
Nationwide Cloud Peering
11
+ More
Connect From Sites into Private Clouds
12
ESnet Private Cloud Connect
13
13
Cloud Solution Co-Design
14
Request
Design
Implement
Operate
ESnet Measurement & Analytics
Ed Balas <ebalas@es.net>
Measurement and Analytics Group Lead
“Heart-Healthy” for Cyberinfrastructure?
We Inject Packets Rather than Dye
When looking for blockage, perfSONAR is the go to
17
Hardware Replaced
Combine Observations with Context
Need to understand the relationships between measurements
18
Vascular System Extends Past ESnet
19
We are Part of a Larger Community
20
Collaboration for End-to-end View
Aggregate Behaviors via Metadata
22
Measure the Whole Stack / Pipeline
23
20+ Years of Measurement Services and Software
24
Component | Type | Host | App | Network | Pipeline |
| Both | | | Throughput, Latency | |
| Software | | | Throughput | |
| Service | | | Flow, Pkt Headers | |
| Software | Planned | Planned | Flow, Interface | Planned |
| Both | Prometheus, Metricbeats, Open Telemetry, Logs | Open Telemetry, Heartbeat | Flow, Interface, Optical, PerfSONAR, BGP | LHC Firefly |
| Software | | | IDS,Flow,protocol and certificate decode | |
IPerf
High Touch
Current Initiatives
25
Stardust as a Service Concept
26
LBNL
ANL
BNL
ORNL
SLAC
JLAB
LSST
LHC
AI-/ML-Based Analytics
Have Needs or Ideas?
Catch me after the talk
28
High Touch: �High-Precision, Real-Time Visibility into Network Traffic
Bruce A. Mah, PhD
Software Engineer, Planning and Architecture Group
ESnet High-Touch
30
ESnet6 High-Touch Platform Deployment
Approximately 40 deployment locations
Focus: Network perimeter coverage
Router packet mirroring allows 100% packet inspection
31
High-Touch Server Hardware Deployment
ESnet6 Core Router
FPGA Servers �(2 per hub site)
AMD Xilinx Alveo U280 FPGA
(1 per server)
2x100G x2
Use Case #1: LHCONE
32
High-bitrate flows were largely, if not entirely, perfSONAR
Everything else “peaks” around 10Gbps, “average” less than 1Gbps
Use Case #2: LSST Troubleshooting
High-Touch hardware inferring loss and retransmission
33
┌─vlan_id─┬─any(sap_routing_instance)─┬─exporting_node─┬─ip_src──────────┬─ip_dst─────────┬─tot_packets─┬─tot_retrans─┬─tot_loss─┬─direction─┐
│ 312 │ LSST │ sunn-ht1 │ 139.229.137.20 │ 134.79.23.9 │ 3045 │ 1005 │ 964 │ in │
│ 314 │ LSST │ slac50s-ht1 │ 139.229.137.20 │ 134.79.23.9 │ 3045 │ 1005 │ 964 │ out │
│ 312 │ LSST │ sunn-ht1 │ 139.229.137.21 │ 134.79.23.9 │ 2567 │ 1069 │ 963 │ in │
│ 314 │ LSST │ slac50s-ht1 │ 139.229.137.21 │ 134.79.23.9 │ 2567 │ 1069 │ 963 │ out │
│ 312 │ LSST │ sunn-ht1 │ 139.229.137.22 │ 134.79.23.9 │ 92627 │ 1592 │ 1531 │ in │
│ 314 │ LSST │ slac50s-ht1 │ 139.229.137.22 │ 134.79.23.9 │ 92627 │ 1592 │ 1531 │ out │
...
│ 312 │ LSST │ sunn-ht1 │ 139.229.180.63 │ 134.79.23.9 │ 52188059 │ 10132615 │ 5342214 │ in │
│ 314 │ LSST │ slac50s-ht1 │ 139.229.180.63 │ 134.79.23.9 │ 52188059 │ 10132615 │ 5342214 │ out │
│ 312 │ LSST │ sunn-ht1 │ 139.229.180.77 │ 134.79.23.251 │ 114203 │ 49 │ 46 │ in │
│ 314 │ LSST │ slac50s-ht1 │ 139.229.180.77 │ 134.79.23.251 │ 117310 │ 50 │ 47 │ out │
│ 312 │ LSST │ sunn-ht1 │ 139.229.180.79 │ 134.79.23.251 │ 323 │ 0 │ 0 │ in │
│ 314 │ LSST │ slac50s-ht1 │ 139.229.180.79 │ 134.79.23.251 │ 323 │ 0 │ 0 │ out │
│ 312 │ LSST │ sunn-ht1 │ 139.229.180.8 │ 134.79.23.9 │ 35787678 │ 459916 │ 337234 │ in │
│ 314 │ LSST │ slac50s-ht1 │ 139.229.180.8 │ 134.79.23.9 │ 35788047 │ 459938 │ 337251 │ out │
│ 312 │ LSST │ sunn-ht1 │ 139.229.180.9 │ 134.79.23.9 │ 37205076 │ 347038 │ 277181 │ in │
│ 314 │ LSST │ slac50s-ht1 │ 139.229.180.9 │ 134.79.23.9 │ 37206401 │ 347047 │ 277181 │ out │
│ 312 │ LSST │ sunn-ht1 │ 139.229.180.97 │ 134.79.23.251 │ 27124 │ 124 │ 73 │ in │
│ 314 │ LSST │ slac50s-ht1 │ 139.229.180.97 │ 134.79.23.251 │ 27787 │ 125 │ 74 │ out │
│ 312 │ LSST │ sunn-ht1 │ 139.229.180.98 │ 134.79.23.251 │ 3324 │ 3 │ 3 │ in │
│ 314 │ LSST │ slac50s-ht1 │ 139.229.180.98 │ 134.79.23.251 │ 3214 │ 3 │ 3 │ out │
│ 312 │ LSST │ sunn-ht1 │ 139.229.180.99 │ 134.79.23.251 │ 7722 │ 17 │ 17 │ in │
│ 314 │ LSST │ slac50s-ht1 │ 139.229.180.99 │ 134.79.23.251 │ 7722 │ 17 │ 17 │ out │
└─────────┴───────────────────────────┴────────────────┴─────────────────┴────────────────┴─────────────┴─────────────┴──────────┴───────────┘
38 rows in set. Elapsed: 15.693 sec. Processed 33.14 billion rows, 1.19 TB (2.11 billion rows/s., 75.62 GB/s.)
Use Case #2: LSST Troubleshooting
Unsampled packet capture shows out-of-order data
34
Packet No. 22
Time = 0.006507154
Seq = 23828; Len = 1322
[TCP Previous segment not captured]
Packet No. 23
Time = 0.006510259
Seq = 21032; Len = 1398
[TCP Out-Of-Order]
Packet No. 24
Time = 0.006511198
Seq = 22430; Len = 1398
[TCP Out-Of-Order]
Packet No. 25
Time = 0.006516453
Seq = 25150; Len = 30
[PSF, ACK]
Measurement and Analytics Integration
35
High-Touch Synopsis
36
Build Your Own Network for Science
John MacAuley
CSA and PPG Group Lead (Acting)
Our Philosophy
38
State of the Industry
39
The Evolving Research Infrastructure
40
Field Site
Instruments
End Site
HPC
SDMZ
Storage
DTNs
The Cloud
End Site
SDMZ
DTNs
Storage
Instruments
Compute
The Network
Wireless
Regional/Intl.
perfSONAR
perfSONAR
perfSONAR
High Touch
High Touch
High Touch
Measurement
Monitoring
In-Network Cache
In-Network Cache
Edge Compute
Edge Compute
Workflows
L2/L3 mesh
Cloud Connect
The API-Driven SENSE Architecture
41
DTN
DTN
DTN
DTN
DTN
UMD
SENSE Orchestrator
SENSE End-to-End Model
Application Workflow Engine
Intent Based APIs with resource discovery, negotiation, and service lifecycle monitoring/troubleshooting
SENSE Resource Manager
RM
RM
RM
RM
RM
RM
RM
RM
Real-time network discovery infrastructure with detailed service ontologies. Dynamic provisioning and monitoring.
But John — this looks really complicated!
42
Absolutely, this is complicated stuff!
But our job is to take this complexity and simplify it for the end user.
Working collaboratively we can peel back the problem space, layer by layer, to find common ground and a path forward.
Hide complexity the user does not need to see and normalize the differences.
Use Case: SENSE and Rucio/FTS/XRootD
43
Rucio
FTS
Scientific Data Management and Movement
Suite
Primary system for LHC and others
End Site
XRootD
(Data Transfer System)
End Site
XRootD
(Data Transfer System)
WAN
1. Rucio identifies groups of "high priority" data flows (IPv6 subnets) and requests “special handling” from SENSE.
1
3. SENSE informs Rucio that requested path has been established.
3
4
4. Rucio starts transfer for the "high priority" data flows.
SENSE
Site RM
SENSE Network RM
SENSE Orchestrator
SENSE
Site RM
2. SENSE takes flows from the site edge and "Traffic Engineers" paths across the WAN and End Sites.
2
Summary
44
To learn more about SENSE
45
Panel