190 likes | 199 Views
This research paper discusses the implementation and benefits of extending dynamic Layer-2 services to campuses using OpenFlow/SDN technology. The study explores the configuration and testing of DYNES in 8 campuses, as well as lessons learned and contributions to the community.
E N D
Extending dynamic Layer-2 services to campuses Scott Tepsuporn and Malathi Veeraraghavan University of Virginia (UVA) mvee@virginia.edu Brian Cashman Internet2 bsc@internet2.edu • April 1, 2015 • FTW Intl. OpenFlow/SDN Testbeds, Miami, FL Thanks to A. J. Ragusa and Luke Fowler (IU), Chin Guok (ESnet), T. Lehman and X. Yang (MAX) – Co-authors on a submitted paper Thanks also to Ezra Kissel (Indiana U), Dale Carder and Jerry Robaidek (U. Wisconsin), Ivan Seskar and Steve Decker (Rutgers U), R. D. Russell and P. MacArthur (U. New Hampshire), Conan Moore (U.Colorado), and Ryan Harden (U. Chicago), Ron Withers (U. Virginia), John Lawson (MARIA), Eric Boyd (Internet2), GRNOC, and several regional REN providers for their support. Thanks to NSF for grants CNS-1116081, OCI-1127340, ACI-1340910, and CNS-1405171, ACI-0958998, and DOE grant DE- SC0011358C
Outline • What was done? • How was it done? • Why do this? • Long-term vision • Contributions to community • Control-plane models • International component
What was done? • Configured DYNES in 8 campuses • WAN multi-domain testbed • What is DYNES? • Eric Boyd, Shawn McKee, Harvey Newman, Paul Sheldon: PIs • NSF MRI project : File Data Transfer (FDT) host + Switch (OpenFlow) + SDN Controller (IDC) + perfSONAR host • 40 universities and 11 regionals • Dynamically created inter-domain L2 paths via OESS GUI (running OSCARS on most DYNES IDCs) • Configured FDT: vconfig, ifconfig, Linux tc • Tested nuttcp and GridFTP: 0 loss?
Campuses involved UNH UWisc I2Lab U. Chicago Rutgers IU MAX CU UVA (UCAR) VTech UTD UH
How was it done? • Method • Brian Cashman: significant help! • For each campus: • Requested logins on FDT with sudo access • Assisted campus admin to install, configure and run OSCARS and OESS • Assisted campus admin to organize static VLANs through campus networks and regionals • Provisioned inter-domain circuits automatically • Provisioned FDTs at end of each circuit manually • Ran nuttcp and GridFTP with htcp/reno and tc rate shaping with cron jobs for loss/throughput
Multi-domain deployment Internet2 ION OSCARS Regional OSCARS OESS Regional Internet2 AL2S OSCARS OESS University University OSCARS OSCARS pS pS OESS OESS ESnet IDC IDC 19 19 FDT FDT OSCARS DYNES DYNES DOE Sites
Examples: End-to-end L2 paths between UVA and IU, and between UVA and UWisc.
Lessons learned • OSCARS and OESS software works well, but .. • When something goes wrong, the error messages are cryptic: error reporting needs community help to improve • Topology approach: scalability? Use DNS? • Tools required for debugging on multi-domain L2 paths • Providers may police rate-guaranteed paths • Need to set tc ceiling (ceil) option; higher throughput at 45 Mbps than at 50 Mbps when circuit through ION was 50 Mbps • It was good to have ION to gain this experience • AuthN/AuthZ • Add DYNES to Shibboleth single-sign service, or • GlobusOnline type service: which is more scalable?
Why pursue this course? • Rate-guaranteed circuits offer a solution to the TCP throughput issue • 0.0046% loss on high BDP paths causes throughput to crash – ESnet SC13 paper • Dynamic L1 circuits • Rates have reached levels where WDM optical circuits are economically viable • L1 now has colorless, directionless, contentionless ROADMs allowing for Rate-guaranteed 100Gbps DTN-to-DTN circuits • Dynamic circuits: solution to the rare big-dataset movement needs of scientific community
Visions of ARPAnet-like growth! Picture taken in LBJ Library, Texas Austin, 60s Exhibit, Oct. 2014
Contributions to community • Extending dynamic L2 service to campuses by having engineers/students gain experience with OSCARS/OESS setup and usage • End-host configuration: use of tc, Circuit TCP to avoid HTCP cwnd changes • Develop: • applications for end-to-end L2 paths • FCAPS: Fault, Config. mgmt, Accounting, Performance monitoring and Security – Management plane • help improve OSCARS and OESS: error reporting/autoconf • CC-NIE awards (ScienceDMZ): many campus deployments; spread this service
Control-plane models • Daisy-chain vs. tree-model • Research literature and PCE IETF work • To avoid lockup of resources: • Daisy-chaining requires limited resource allocation on forward signaling path • Multiple start-time options to increase chance of success • Fast processing • Tree-model AuthN needs? • Global PSTN: no customer-provider relationships required with providers more than two hops away in daisy-chain model. Not so in tree model • Testbed view (GENI) vs. ARPAnet growth view
International component • Added Keio University, Yokohama, Japan • OSCARS successfully set up L2 circuit • ping didn’t work • need to create trouble ticket
Requesting your feedback • One approach • Grow this deployment to CC-NIE/other DYNES sites • Create a virtual organization of individuals to develop tools for diagnostics, improve OSCARS, OESS, develop applications • Second approach • Add Aggregate Manager and contribute this testbed to GENI for networking researchers • Third approach • Develop L1 (WDM optical) SDN testbed
nuttcpthroughput for paths through AL2S (blue) and ION (red).
R: max rate guaranteed by tc; C: Ceiling limits max sending rate
GridFTP tests • Disk-to-disk transfers. • 20 GiB * 1 file for ‘single’ • 20 MiB * 1024 files for ‘LOSF’. • tc=C, 3 Gbps • -fast, -pp, and -cc 16 used GridFTP reported throughput for paths through AL2S. LOSF=Lots of Small Files