1. TeraPaths TeraPaths: establishing end-to-end QoS paths - the user perspective Presented by Presented by Dimitrios Katramatos, BNL Dimitrios Katramatos, BNL

2. 2 Outline  What is TeraPaths?  Motivation  Concept and implementation  View of the world  How can it be used?  Admins:  Installation and configuration  Security model  Users:  Web interface  API/CLI  Integration  Status/future

3. 3 Motivation  The problem: support efficient/reliable/predictable peta-scale data movement in modern high-speed networks  Capacity is not limitless  Multiple data flows with varying priority  Default “best effort” network behavior can cause performance and service disruption problems  Solution: enhance network functionality with QoS features to allow prioritization and protection of data flows  Classify traffic  Schedule network usage

4. 4 TeraPaths TheTeraPaths Service: Reserve End-to- End Paths with Guaranteed Bandwidth WAN WAN web services TeraPaths

5. 5 Prioritized vs. Best Effort Traffic

6. 6 How?  Make arrangements at end (TeraPaths-controlled) sites  Check local site availability and reserve temporarily  Check remote site availability and reserve temporarily  Pick alternative time slot if requested slot taken and iterate  Make arrangements with WAN  Request MPLS tunnel or dynamic circuit with matching bandwidth and duration  Confirm and commit  …if all parties agree…  …otherwise fail  Timer activated tasks configure network devices  Verify status of all reservations and run configuration tasks (WAN services do their part of the setup)  Fail otherwise

7. 7 Conceptual View of the Network TeraPaths Site A Site B Site C Site D WAN 1 WAN 2 WAN 3 service invocation data flow peering WAN chain

8. 8 TeraPaths Testbed ( ) current

9. 9 Administration  Software installation  Web service modules on SJSAS  JVM, MySQL  Software configuration  Server security  Module locations  Database  Site router configuration  Classes of service, policing, PBR  DSCP trust  VLANs (for L2 support – dynamic WAN circuits)

10. 10 TeraPaths TeraPaths Web Services Architecture Internal Services Public Services Web Interface Admin Module NDC Database protected network API remote local WAN Services WAN Services proxy CLIs/w client

11. 11 Security Model  Current: “circle of trust”  Client-side and server-side authentication  Routers get configured through ssh from specific controlling hosts (preferably physically connected)  Servers “talk” only to known servers (certificates)  Hosts only “talk” to known hosts (firewalls)  Servers only accept users with known certificates (DOE grid)  Local user login  User needs at least one local account to enter  In the works: grid-style  GUMS/VOMS

12. 12 Site Setup

13. 13 Necessary Info  User data for AAA  Data flow ID  Source IP and port  Destination IP and port  IPs and ports can be ranges (multiple flows)  Direction (unidirectional/bidirectional)  Protocol  Bandwidth (class of service)  Multiple flows will share (best effort within the class)  Start time and duration  Minute resolution

14. 14 Web Interface (i)

15. 15 Web Interface (ii)

16. 16 Web Interface (iii)

17. 17 Web Interface (iv)

18. 18 Web Interface (v)

19. 19 Web Interface (iii-b)

20. 20 Web Interface (vi)

21. 21 API/CLI and Integration  Web Interface uses API  CLI uses API  Users can invoke CLI/API from their scripts/applications  Popular data transfer software plug-ins (e.g. dCache)  Life is easier because transfer tool knows flow id data  API will be extended for use by other network path-building and scheduling services (e.g., services being developed in US LHCNet, UltraLight/PLaNetS)

22. 22 Status and Future  Currently: basic software ready  API and web interface, simple negotiation  Statically allocated bandwidth classes  L3 paths (MPLS tunnels) through ESnet  Elementary AAA  BNL  UMich  In the works, future  CLI, extended API, configurable negotiation  Dynamic bandwidth allocation  L2 paths (dynamic circuits) through ESnet and Internet2  Grid-style AAA  Admin module to facilitate site setup  Expansion to T2 sites  http://www.racf.bnl.gov/terapaths

23. 23 Prioritized vs. Best Effort Traffic