1 / 44

Proposed Diffserv Evaluation for Emerge Sites

Proposed Diffserv Evaluation for Emerge Sites. Volker Sander sander@mcs.anl.gov Argonne National Laboratory 1/20/2000. Outline. Basic GARA overview New GARA-features Basic set of experiments Installation of GARA Running the experiments using GARA Timeline.

powa
Download Presentation

Proposed Diffserv Evaluation for Emerge Sites

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Proposed Diffserv Evaluation for Emerge Sites Volker Sander sander@mcs.anl.gov Argonne National Laboratory 1/20/2000

  2. Outline • Basic GARA overview • New GARA-features • Basic set of experiments • Installation of GARA • Running the experiments using GARA • Timeline

  3. Aggregate based scheduling implements EF PHB The Basic Diffserv Concept Flow based Classify and Mark packets Shape Traffic Classify and Mark packets Shape Traffic

  4. Proposed Implementation Server Client GARA API GARA Diffserv Resource Manager

  5. The Multidomain Extension Server Client GARA API GARA Diffserv Resource Manager GARA Diffserv Resource Manager

  6. GARAGlobus Architecture for Reservation and Allocation • Three important contributions: • Support for Advance Reservations (AG) • Uniform treatment of underlying resources • Network, disk, CPU etc… • Currently supported: Differentiated Services, DPSS, and DSRT • Layered architecture enables generic co-reservation agents • User is able to select API best suitable for his need

  7. GARA Basics—Reservations • There is a generic “reservation”, which has several properties: • Start Time (“now” or future) and Duration • Resource type/Underlying resource identifier • Resource-specific (bandwidth, % CPU…) • All reservations are treated uniformly: • Create/Modify (Given properties) => Returns Reservation Handle • Destroy • Monitor (Callbacks or Polling)

  8. Gatekeeper (Authenticate and Authorize) User Program or Agent Gatekeeper Service Reservation Handle Local Resource Manager API (LRAM) Resource Manager Resource (Router...) A picture of what happens(creating a reservation) Create

  9. Resource Manager Setup reservation User Program bind(handle) LRAM API Resource Enforce Reservation A picture of what happens(claiming a reservation) Note: GARA supports third party binding

  10. Example: Network reservation • In advance, make a reservation: • RSL: & (reservation-type=network) (start-time=now) (duration=3600) (endpoint-a=128.135.11.4) (endpoint-b=128.135.11.1) (bandwidth=1000) (protocol=udp) (reservation-subtype=low-latency) • Handle: Opaque string H1 • At run-time: • Bind(H1,RSL) • RSL: & (which-endpoint=a) (endpoint-a-port=5000) (endpoint-b-port=5000)

  11. 100% % of available resource allocated 0% Time The Resource Manager • To track advanced reservations, we use a simple “slot table” • We assume exclusive access to resource through the resource manager • We aren’t tied to this particular resource manager

  12. End-to-End Co-Reservation Agent MDS Resource Manager Resource Manager Workstation User process End-to-End Network Reservations • Algorithm for a single network reservation • Discover which gatekeepers/resource managers need to be contacted (MDS) • Make reservation at each one.

  13. The GARA API • globus_gara_reservation_create() • Gatekeeper contact • RSL reservation specification • Reservation Handle or Error • globus_gara_reservation_modify() • Old Reservation Handle • RSL reservation specification • New Reservation Handle or Error

  14. The GARA API (continued) • globus_gara_reservation_cancel() • Reservation Handle • Error • globus_gara_reservation_status() • Reservation Handle • Status/Error • globus_gara_reservation_callback_register() • Reservation Handle • Callback Function/User Parameter • Error

  15. New GARA features • New Reservation-Subtypes • low-latency • Used to support jitter sensitive applications using the same EF aggregate behavior as high-throughput TCP applications • Based on traffic shaping and Priority-Queuing • Currently being evaluated • background • Used to support bulk transfers, including deadline support. Takes at least the amount of premium traffic required to fulfill the deadline; more if not used actively • Monitoring of the network edges • Provides feedback to applications when they send too fast

  16. Network + CPU Reservations

  17. Example of bulk transfer (LAN)

  18. Example of bulk transfer (WAN)

  19. Feedback from Monitoring the Edges

  20. Evaluation Tools • UDP Traffic Generator • Modified Version of Andy Adamson’s gen_send and gen_recv • Evaluate admission control • Creating competing traffic • MGEN/Drec • Evaluate delay and Jitter for Premium UDP Flow • Modified Version of ttcp • GARA-enabled (wait for reservation) • Support for a desired application rate • long term control • short term control • Consecutive bandwidth reporting • Bulk transfer ttcp

  21. Basic Experiments • Evaluate Admission Control • Evaluate premium TCP Flows under Congestion • Analyze network traces with tcpdump • Evaluate UDP • Delay • Jitter • Evaluate Inter-Domain Issues Fundamental idea: Get the necessary knowledge to be able to experiment with REAL applications

  22. Basic Experiment I • Goal: Proof of Admission Control • Gather packet statistics from gen_recv for different configurations and different traffic profiles:

  23. Basic Experiment I gen_recv gen_send GARA Diffserv Resource Manager

  24. Basic Experiment II • Goal: Proof of Premium Quality for TCP flows • Run modified ttcp with different traffic and reservation profiles; gather receiver bound statistics • Create congestion using gen_send/recv

  25. Basic Experiment II • Enhancement • Use tcpdump and tcptrace get a deep overview on the behavior • Use netlogger_enabled ttcp_gara and gen_recv to publish data into MDS. “Real Time Visualization”

  26. ttcp -r gen_send gen_recv ttcp -t Basic Experiment II GARA Diffserv Resource Manager

  27. Basic Experiment III • Goal: Demonstrate Premium Quality for UDP flows • Run mgen/drec with different traffic and reservation profiles; gather receiver bound statistics • Create congestion using gen_send/recv

  28. drec gen_send gen_recv mgen Basic Experiment III GARA Diffserv Resource Manager

  29. Basic Experiment IV • Goal: Proof Premium Quality for UDP flows sharing one EF aggregate • Run mgen/drec with different traffic and reservation profiles; gather receiver bound statistics • Run high-throughput ttcp using a correct reservation • Create congestion using gen_send/recv

  30. ttcp -r gen_send gen_recv ttcp -t mgen drec Basic Experiment IV GARA Diffserv Resource Manager

  31. Additional Experiments • Bulk-Transfer • Reevaluate inter-domain behavior • Add Traffic-Shaping between domains • Test Inter-Domain Admission control • Prepare the Instrumentation • Go with real applications

  32. Installing GARA • Get GARA • (currently through E-Mail from sander/roy @mcs.anl.gov) • Get SSLeay 0.9.0 and install it • Get Globus 1.1 configure and compile it deploy is not necessary for doing tests but recommended Run grid-cert-request to apply for a Grid X509 Certificate add “gara-service stderr_log,local_cred - $GARA_DIR/gara/programs/globus_gatekeeper_gara_service -d” to $GLOBUS_DEPLOY_DIR/etc/globus-services • Read gara/docs/* • Edit gara/build • Run gara/build • Customize GARA • gara/resource_manager/programs/diffserv_manager.conf • gara/resource_manager/programs/setup_flow.cfg • (Samples are in the documentation directory)

  33. Building GARA • $GARA_DIR/build • #!/bin/ksh • CC=cc • CXX=CC • CFLAGS="-g -v -mt" • GLOBUS_DIR=/soft/pub/packages/globus-1.1.0/development/sparc-sun-solaris2.7_pt • hreads_standard_debug • SSL_LIBRARY_DIR=/soft/pub/packages/SSLeay-0.9.0/lib • export CC CXX CFLAGS GLOBUS_DIR SSL_LIBRARY_DIR • configure • make clean • make depend • make all • # • # For portability reasons you might not want to do a make withdsrt.. • # in case: just comment out this line. • #make withdsrt • Run build

  34. Configuring GARA • resource_manager/programs/diffserv_manager.conf PublicationMethod webmds LDAPDistinguishedName "dslnet1.mcs.anl.gov:34880:/C=US/O=Globus/O=Argonne Nati onal Laboratory/OU=MCS/CN=roy” MDSPublishPassword “password” WEBPublishFile /home/sander/public_html/diffserv_manager_slots.html NoOfRouters 2 IPAddressesServed[1] 140.221.48.162,140.221.48.146,140.221.48.164,140.221.48.1 65,140.221.48.166,140.221.48.167,140.221.48.34 IPAddressesServed[2] 140.221.48.98,140.221.48.114,140.221.48.102,140.221.48.10 3,140.221.48.104,140.221.48.105 • Parameters: "LDAPDistinguishedName", "MDSPublishPassword", "WEBPublishFile", "FILEPublishFile", "Quantity", "ClearSlotTable", "SlotTableFilename", "Verbose", "PublicationMethod", "DontReallyBindReservations"

  35. Configuring GARA • resource_manager/programs/setup_flow.conf 1_ROUTER 140.221.48.145 1_USERNAME my_userid 1_PASSWORD password 1_INTERFACE1 FastEthernet1/0/1 140.221.48.162 1_INTERFACE2 FastEthernet1/0/1 140.221.48.164 1_INTERFACE3 FastEthernet1/0/1 140.221.48.165 1_INTERFACE4 FastEthernet1/0/1 140.221.48.166 1_INTERFACE5 FastEthernet1/0/1 140.221.48.167 1_INTERFACE6 FastEthernet1/0/0 140.221.48.146 # # 2_ROUTER baku 2_USERNAME my_userid 2_PASSWORD password 2_INTERFACE1 FastEthernet1/0/1 140.221.48.98 2_INTERFACE2 FastEthernet1/0/1 140.221.48.102 2_INTERFACE3 FastEthernet1/0/1 140.221.48.103 2_INTERFACE4 FastEthernet1/0/1 140.221.48.104 2_INTERFACE5 FastEthernet1/0/1 140.221.48.105 2_INTERFACE6 FastEthernet1/0/0 140.221.48.114

  36. Setting up the routers • Get new IOS XE beta release IOS (tm) RSP Software (RSP-PV-M), Experimental Version 12.0(19991129:193607) [rolsen-conn_isp_llq 144] Available at ftp://ftpeng.cisco.com/rolsen/rsp-pv-mz.120699 • Edge-Routers (Update of setup_flow required) class-map match-all EF match ip dscp 46 class-map match-all priority-qos match qos-group 99 policy-map emerge class EF bandwidth 30000 queue-limit 500 class priority-qos priority policy-map set-precedence • Attach service-policy set-precendence to every input • Attach service-policy emerge to every output interface

  37. Setting up the routers • Interior-Routers (Update of setup_flow required) class-map match-all EF match ip dscp 46 policy-map emerge class EF bandwidth 30000 queue-limit 500 • Attach service-policy emerge to every output interface

  38. Updating setup_flow • setup_flow is the script which is configuring the router • Possible update of setup_flow (is) 197 expect_after default { close; continue } 198 199 expect "name: " { send "$username\r" } 200 expect "word: " { send "$password\r" } • Might be (without tacacs+) 197 expect_after default { close; continue } 198 199 expect ”word: " { send "$password\r” } 200 expect “#” { send “enable\r” } 201 expect "word: " { send "$password\r" }

  39. Updating the MDS • End-to-end API searches for end-systems in MDS • Publish information for all end-systems into MDS dslnet1.cldif: --------------------- dn: hn=dslnet1.mcs.anl.gov, ou=Mathematics and Computer Science Division, o=Argonne National Laboratory, o=Globus, c=US …. If the machine is already in MDS this is enough networkreservationcontact: dslnet1.mcs.anl.gov:30000:/C=US/O=Globus/O=Argonne National Laboratory/OU=MCS/CN=roy197 expect_after default { close; continue } • run grid-info-update • Tools will be available soon

  40. The GARA Source Tree • Subdirectories represent different layers • end2end • gara (gara/java GUI) • lram • resource_manager • slot_manager • common • logging • simple_multi • (dsrt) • We are providing examples for every layer • docs directory contains lots of useful information

  41. Doing Further Tests • Select your favorite application • Determine port numbers • edit (set endpoint systems) and run script: gara/gara/utilities/demo_make_reservation • Create congestion • Try demo_modify_reservation for getting different premium bandwidth • Try demo_cancel_reservation • Or use the GUI

  42. Timeline • Establish connectivity (January) • mostly done! • Setup accounts for Emerge-User (January!) • Check connectivity • Install and customize GARA (Jan - Feb) • partly done • Configure and check with GUI without any application (Just look at differv_manager and router) • Do basic experiments (February-March) • Start with multi-domain issues (March-April) • Port real applications to the Testbed (Feb-?)

  43. Questions... • Now or later… (sander/roy @ mcs.anl.gov)

More Related