1 of 46

Not Just Fast Data: �ESnet Networking Services to Enable Science

Jon-Paul Herron

Dale W. Carder

Ed Balas

Bruce Mah

John MacAuley

2 of 46

Overview of ESnet Advanced Services

Jon-Paul Herron

Department Head, ESnet Network Services

3 of 46

ESnet’s Service Philosophy: What Really Matters

  • Infrastructure
    • Reach: We have to be in the right places
    • Security, Availability, & Performance: Our services need to work
    • Flexibility & Agility: We have to be able to change quickly
    • Visibility: We should be proactively transparent
  • Users
    • Understand Science Needs: We anticipate where science is going
    • Collaborate: We work with our users to build just what they need

3

4 of 46

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

5 of 46

ESnet Infrastructure By the Numbers

5

AVAILABILITY

PERFORMANCE

REACH

6 of 46

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

7 of 46

Co-designed

Solutions

  • Enabled by Engagement
  • Goal:
    • On-demand solutions
    • Integrated into workflows

7

1

3x

1x

8 of 46

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

9 of 46

ESnet Cloud Services

Dale W. Carder

ESnet Network Engineering

10 of 46

ESnet-Enabled Public Cloud Examples

10

11 of 46

Nationwide Cloud Peering

11

+ More

12 of 46

Connect From Sites into Private Clouds

  • Proven L2VPN Solution built upon OSCARS
    • Dedicated Bandwidth
    • Flexible
    • Resilient
    • Secure

12

13 of 46

ESnet Private Cloud Connect

13

13

14 of 46

Cloud Solution Co-Design

  • Each cloud service instance tends to have unique needs
  • Consultation & co-design process
    • Connection to Site
    • Handoff to Cloud
    • Resilience at either end & through ESnet
    • Security

14

Request

Design

Implement

Operate

15 of 46

ESnet Measurement & Analytics

Ed Balas <ebalas@es.net>

Measurement and Analytics Group Lead

16 of 46

Heart-Healthy” for Cyberinfrastructure?

  • Congestion, blockages, failures happen here too

  • Measurement and monitoring is preventative care

17 of 46

We Inject Packets Rather than Dye

When looking for blockage, perfSONAR is the go to

  • Throughput
  • Loss
  • latency

17

Hardware Replaced

18 of 46

Combine Observations with Context

Need to understand the relationships between measurements

  • Location, topology,
  • Associated organizations

18

19 of 46

Vascular System Extends Past ESnet

19

20 of 46

We are Part of a Larger Community

20

21 of 46

Collaboration for End-to-end View

22 of 46

Aggregate Behaviors via Metadata

22

23 of 46

Measure the Whole Stack / Pipeline

23

24 of 46

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

25 of 46

Current Initiatives

  • End-to-end R&E visibility
    • Create composite view of infrastructure
    • Employ federated identity / zero trust for controlled sharing
    • Improved mapping

  • Innovative ops using AI/ML
    • employ intuitive interfaces to complicated data
    • Look for insights and anomalies

25

26 of 46

Stardust as a Service Concept

  • Dedicated resource for community
    • Production 24/7 system
    • Provide an authenticated end to end view
    • Role based access control

  • Standardized Offering:
    • One stop shop: Net, Host, App
    • Grafana, Jupyter, my.es.net for analysis
    • Appropriate ingest rate and data retention

  • Key Features
    • End-to-end view of pipelines
    • View of all layers in stack
    • Federated Auth for controlled sharing
    • multi-tenancy supporting virtual orgs.
    • Relationships between data types

26

LBNL

ANL

BNL

ORNL

SLAC

JLAB

LSST

LHC

27 of 46

AI-/ML-Based Analytics

  • Forecast future resource use
  • Natural Language Interfaces
  • Incident similarity
  • Incident summary

28 of 46

Have Needs or Ideas?

Catch me after the talk

28

29 of 46

High Touch: �High-Precision, Real-Time Visibility into Network Traffic

Bruce A. Mah, PhD

Software Engineer, Planning and Architecture Group

30 of 46

ESnet High-Touch

  • High-precision real-time network telemetry and measurements
  • Programmable hardware and software
  • Network visibility to deliver better services
    • Flow- and packet-level
    • Line-rate for multiple links
    • Network engineering, troubleshooting, security, etc.

30

31 of 46

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

32 of 46

Use Case #1: LHCONE

  • Flow-level measurements of LHCONE traffic
    • Data transfers are much slower than commonly believed
    • No signs of packet loss / congestion

32

High-bitrate flows were largely, if not entirely, perfSONAR

Everything else “peaks” around 10Gbps, “average” less than 1Gbps

33 of 46

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 │ 101326155342214 │ in │

│ 314 │ LSST │ slac50s-ht1 │ 139.229.180.63 │ 134.79.23.9 │ 52188059 │ 101326155342214 │ 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 │ 459916337234 │ in │

│ 314 │ LSST │ slac50s-ht1 │ 139.229.180.8 │ 134.79.23.9 │ 35788047 │ 459938337251 │ out │

│ 312 │ LSST │ sunn-ht1 │ 139.229.180.9 │ 134.79.23.9 │ 37205076 │ 347038277181 │ in │

│ 314 │ LSST │ slac50s-ht1 │ 139.229.180.9 │ 134.79.23.9 │ 37206401 │ 347047277181 │ 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.)

34 of 46

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]

35 of 46

Measurement and Analytics Integration

  • Shared metadata for networks, sites
  • High-Touch flow data available to Stardust
    • Cross-checking flow data sources (High-Touch vs. IPFIX)
    • Enables joint visualization across data sources
    • Enables joint analytics

35

36 of 46

High-Touch Synopsis

  • High-Touch uses a combination of programmable hardware and software to collect high-fidelity data on network traffic.�
  • ESnet has developed and deployed this internal service with the goal of providing a better network experience.

36

37 of 46

Build Your Own Network for Science

John MacAuley

CSA and PPG Group Lead (Acting)

38 of 46

Our Philosophy

  • Understand Science Needs: Anticipate where science is going
    • We listen to our users through requirement reviews, public forums, and daily interactions.

  • Collaborate: Work with our users to build what they need
    • We develop foundational network services, add-on software services, and domain specific solutions.
    • With our partners we rapidly prototype new concepts.
  • Co-design: Consult, design, test, and support
    • Deliver capabilities within the network that can be programmatically consumed by your scientific workflows.
    • Provide solutions to control resources not only within ESnet, but wherever resources are consumed.

38

39 of 46

State of the Industry

  • Science workflows engage cyber infrastructure to accomplish a complex set of tasks
    • Rely on access to heterogeneous resources across distributed facilities.
    • Desire workload mobility between facilities for diversity and availability.
    • The Integrated Research Infrastructure (IRI) will provide key building blocks.
  • Managing these diverse workloads can be overwhelming
    • Workflows must communicate directly with target facilities when consuming resources, dealing with both diverse access methods, and varying behaviors.
  • Perhaps a network-aware middleware solution is warranted to abstract complexity?
    • Provide tools for end-to-end resource orchestration, enabling scientific workflows to dynamically interface with the full infrastructure stack while minimizing operational overhead.

39

40 of 46

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

41 of 46

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.

42 of 46

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.

43 of 46

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

44 of 46

Summary

  • The IRI vision is important to the future of the DOE complex�
    • Defines a normalized set of services and resources, exposing via consistent API and models.
    • Supports extensions for unique capabilities when needed.
    • Demonstrates a working collaboration across facilities.
  • SENSE provides our end users the capability to build their own virtualized network for science�
    • Provides value added tooling to simplify the creation of end-to-end workflows.
    • Exposes a simplified intent-based API to the end user, hiding the complexity of the cyber infrastructure.
  • Collaboration and co-design are key to our combined success�
    • Individually we cannot provide a complete end-to-end solution.
    • Co-designed solutions are built with a shared sense of ownership.
    • We align on goals, can anticipate challenges earlier, and integrate diverse perspectives.

44

45 of 46

To learn more about SENSE

45

46 of 46

Panel