BEN: Breakable Experimental Network

Transcription

1 BEN: Breakable Experimental Network Nick McKeown Stanford University Presenter: Munhwan Choi

2 Overview Requirements and motivation BEN overview Basic resources Fiber infrastructure and connectivity Functional Design Physical Design and implementation Use cases

3 High-level Requirements Facilitate network research Network researcher managed facility Empower experimenter by giving full control of resources Provide programmable and configurable network resources No production network requirements Facilitate high performance networking Integrate Visualization, SAN and HPC technology resources Support applications research Connect camps engagement sites

4 Technology Innovation Motivation for Implementing BEN High Production Network e.g., Service Provider Static Networking Commodity Internet High availability R&E Network e.g., I2, NLR Advanced services High Performance Applications Research Expected reliability Breakable Network e.g., Network Research Layer 1-7 configurability Vertical integration capability New technology testing Hybrid/complex networks Reliability for experiment Low Researcher Control of Resources High

5 What is BEN? BEN is an experimental fiber facility Will support experimentation at metro scale Distributed applications researchers Networking researchers Not a production network Main goal: enabling disruptive technologies Shared by the researchers Coarse-grained time sharing is the primary mode for usage Assumes some experiments must be granted exclusive access to the infrastructure

6 BEN fiberplant Combination of NCNI fiber and campus fiber Possible fiber topologies:

7 BEN Fiber Responsibilities Cooperative effort between NCREN, Duke, NCSU, UNC and Renci Preemptive service to assist urgent production needs Initial use case is to connect Renci engagement sites

8 UNC-Renci Connectivity Detail

9 Hierarchical Power Distribution Model Enables hierarchical control of power Provides researcher with ability to remotely power cycle experimental equipment Accessible via BEN management network

10 BEN PoP Functional Architecture

11 BEN Implementation - Node Design

12 BEN Implementation - Network Management BEN Node Physical Connectivity Logical Diagram of Management Plane Connectivity Management plane enables reliable and independent paths of interconnectivity between BEN nodes Full-mesh of routed tunnels ensures redundant connectivity using private addressing

13 BEN Node Network Management Management plane facilitates console, network management and power connectivity for the experimenter to remotely control their equipment

14 Remote Access OpenVPN solution for remote access to the BEN Gateway NAT implementation on BEN Gatweway BEN management network defaults to BEN Gateway

15 Supporting Systems DNA - Infinera s Digital Network Administrator Nagios - server and network monitoring tool DNS - domain names include duke.ben, ncsu.ben, unc-ch.ben and renci.ben

16 Security User s will login through the BEN Gateway and directly access the equipment using Radius and/or LDAP for authentication and authorization RFC Private addressing Each location has one public IP address on the SSGs security appliance Traffic between SSGs is encrypted in IPSec tunnels Need to address external connectivity via FrameNet & DCN(NCREN) ACLs & Firewalls Netflow

17 Use Case: Pt-2-pt Traffic Generation

18 Use Case: Visualization Application Using Remote HPC Resources

19 BEN governance and usage BEN is a shared resource for advancing the state of experimental science in the Triangle BEN is controlled by the researchers engaged in experimental activities on it BEN Experimenter Group (BEN-EG) Resource allocation and management is done entirely by the researchers themselves

20 BEN Usage Experimental equipment connected to the BEN fiberplant at BEN points-of-presence Use fiber distribution panels (FDP) or MEMS fiber switches to switch experimental equipment in and out Based on the experiment schedule By nature of the facility, experiments running on it may be disruptive to the network BEN is not meant to be a fast and reliable bit-pipe between campuses BEN Points of presence located at the RENCI engagement sites and RENCI anchor site

21 RENCI BEN Equipment Configuration

22 Resources accessible from BEN IBM Blue Gene/L Cluster 2,048 compute nodes 11.4 TF peak performance 70 Dell PowerEdge 1955 blades 35 compute nodes running Linux Rear-projection vis walls HD stereoscopic projection system TUCASI Research Storage System 200TB in Phase I 1.5PB in Phase II GigE and 10GigE Social computing room Dome display 4K projection room

23 Research Possible uses of BEN Physical layer experimentation Control plane research Hybrid networking research Cross-layer research Education Allow students to work on real equipment

24 BEN Experimenter Group BEN-EG is the body responsible for managing BEN resources Multiple teams of researchers can run experiments on BEN Each team has a representative in the Group to speak for the needs of the team Only teams actively engaged in running experiments on BEN have representatives in the Group

25 Responsibilities of the Group The Group is responsible for sharing BEN resources It s main functions are Scheduling of resources Conflict resolution Some experiments can run concurrently, others may require the exclusive use of the entire facility

26 BEN Redux Reconfigurable optical plane We will be seeking out opportunities to expand the available fiber topology Researcher equipment access at all layers From dark fiber up Coarse-grained scheduled Researcher-controlled No single-vendor lock-in Equipment with exposable APIs Connectivity with substantial non-production resources

27 Current state of BEN RENCI s equipment on BEN will be ready in 1 month Work underway To splice the fiber Have power and equipment racks ready at BEN points of presence Collaborative proposals using BEN: Building an integrated GENI island using BEN (with Jeff Chase, Duke) Experimenting with network virtualization using SILO framework (with NCSU) BEN Day Visit by interested faculty of available BEN sites

28 Planned Near-term RENCI Research on BEN Enabling remote HD visualization Multi-screen HD viswalls with data striped across multiple wavelengths 4K video distribution Transporting 4xHD signal across the network Programmable networked platforms Bigger/better netfpga? Component for large Triangle-wide proposal activities GENI Cross-layer interactions Interactions between the optical plane and the packet forwarding plane

29 SILO Project Traditional and SILO stacks App App App App App App Transport Transport m 11 m 11 m 13 m 21 m 21 Network Data Link Cross- Service Tuning m 31 m 21 m 31 m 31 silo & service mgmt Physical Physical Channels Tuning strategies, hints m 42 m 43 m 62 m 62 m 61 Physical Channels Composability Constraints

30 Tuning and Management Control SILO Project Stratified Network - Graded Entry Transport in layers, control across layers Single Point of Policy and Certification Generic Authentication Portable Configuration Need-based per-flow stacks Redundant Path Delivery Composable Service with Control Interface Smooth integration of evolving services, security, etc. A Big Picture??? (Future Service)

31 Reference ben.renci.org Ben Day 2008 Presentation slides

32