1 / 31

AR-PIN/PDC: Flexible Advance Reservation of Intradomain and Interdomain Lightpaths

AR-PIN/PDC: Flexible Advance Reservation of Intradomain and Interdomain Lightpaths. Eric He, Xi Wang, Jason Leigh Electronic Visualization Laboratory University of Illinois at Chicago GRIDNETS 2006 October 1, 2006. LambdaGrid Requirements. Massive bandwidth DWDM

jolene
Download Presentation

AR-PIN/PDC: Flexible Advance Reservation of Intradomain and Interdomain Lightpaths

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. AR-PIN/PDC: Flexible Advance Reservation of Intradomain and Interdomain Lightpaths Eric He, Xi Wang, Jason Leigh Electronic Visualization Laboratory University of Illinois at Chicago GRIDNETS 2006 October 1, 2006

  2. LambdaGrid Requirements • Massive bandwidth • DWDM • Quality of Service guarantee • Dedicated lightpaths • Dynamically configurable by various applications • Web services • Collaboration from multiple domains • Inter-domain • Advance reservation • Flexible We want to get rid of ROUTERS!

  3. Proposed Solution • AR-PIN/PDC: A software system to let applications control both intra-domain and inter-domain lightpath resources through web services, with flexible advance reservation capability. AR-PIN/PDC: Advance Reservation Photonic Inter-domain Negotiator / Photonic Domain Controller

  4. Outline • Flexible Advance Reservation Model • AR-PIN/PDC Architecture • Simulation Results • Deployment and Experiments • Future Work

  5. Flexible Advance Reservation Model s, d: source and destination nodes. tstart, tend: the reservation window range. tmd: minimal duration. c: criteria, such as the earliest, the longest.

  6. AR-PIN/PDC Architecture Peer-to-Peer Topology Advertisement AR-PIN 1 AR-PIN 1 AR-PIN 1 Web Services Web Services Web Services Topology Database Topology Database Topology Database Signaling Signaling Signaling AR-PDC1 AR-PDC1 AR-PDC1 Slot Table Slot Table Slot Table Device Driver Device Driver Device Driver TL1 control messages Client B Client A Photonic Switches Lightpath

  7. Web Services • Web services for applications • advanceReserveHH/SH/SS • immediateReserveHH/SH/SS • claim • unbind • terminate • modify • renew

  8. Client Sample package edu.uic.evl.pdc.client; import java.util.*; public class claim { public static void main(String [] args) { try { PDCService service = new PDCServiceLocator(); PDCEndpoint endpoint = service.getPDCEndpointPort(); endpoint.claim(args[0]); } catch(Exception e) { e.printStackTrace(); } } }

  9. Interdomain Routing A E B 1 2 C D 3 F G Border Switch Internal Switch 1,2,3 Domain ID A,B,C… Border Switch ID • Domains separated at Switches. • Border Switch ID is globally unique. • Exchange topology summary only. • Exchange in publish/subscribe mode.

  10. 2D Matrix Join Operation Wavelength Join = Time Slot Both intra-domain and inter-domain

  11. AR-PDC Device Driver • Unified interface. • The drivers talk to devices using TL1.

  12. Simulation • How the flexibility affects the blocking rate and resource utilization? • How advance reservations affect immediate reservations? • How to divide resources between advance reservations and immediate reservations? • Define the degree of flexibility:

  13. Blocking Rate Under Different Flexibilities

  14. Resource Utilization Under Different Flexibilities

  15. When ARs and IRs co-exist- Partition or Share Wavelengths? Shared case has much lower blocking rate!

  16. However, IRs may be dropped for shared case! • It is possible for IRs to be dropped (preempted) by ARs. In order to maintain a certain Quality of Service, we can add one more parameter for IRs: Minimum Duration. • It is still acceptable if we could • satisfy the Minimum Duration • notify the user in advance • In another word, being dropped is better than being blocked! • Therefore, we need to add admission control for IRs. AR IR time IR has be to dropped out

  17. Blocking Rate of IRs for Different Minimum Duration • IR load is fixed. • More ARs, IR blocking rate increases. • Longer MD, IR blocking rate increases.

  18. Admission Control for ARs • If there is no admission control for ARs, it is possible for IRs to be blocked seriously, even starved, because of the time advantage of ARs. • A good method is to reserve some wavelengths only for IRs. e.g., ARs can only use 5 of 8 wavelengths.

  19. We also need AR Admission Control

  20. Findings From Simulations • By introducing some flexibility on the time parameters of advance reservations, the system performance can be improved dramatically. • IR minimum duration is necessary to have good Quality of Service. • AR admission control is necessary in order to maintain a well-balanced AR/IR mixed environment.

  21. Photonic Testbed Topology rembrandt node 3-6 Glimmerglass NetherLight AR-PIN/PDC control plane AR-PIN/PDC cluster node 1-4 AR-PIN/PDC AR-PIN/PDC scylla node 11-16 Calient Glimmerglass EVL Glimmerglass UCSD StarLight yorda node 11-16 charybdis nic 1-2 atlas nic 1-2

  22. AR-PIN/PDC Web Interface - Schedule

  23. AR-PIN/PDC Web Interface - View

  24. S-C prop Parallel Claims EVL SL UCSD UvA C-S prop EVL-SL EVL-UCSD EVL-UvA EVL-SL-UCSD-UvA

  25. Future Work • LambdaBridge: An edge-based strategy to “bridge” applications on lambda networks. • Manage and adapt application flows and provide cluster-to-cluster lambda connections. • Will be presented in BroadNets 2006.

  26. Thank you!AndQuestions?http://www.evl.uic.edueric@evl.uic.edu

  27. Interdomain Reservation Process PIN1 PIN4 PIN2 PIN3 A B 1. Client A sends a lightpath request to PIN1 2. PIN1 Find doman-level route from topology database. 3. Send probeRequest msgs to other domains in parallel. 4. Each domain gathers resource availability info and sends it to PIN1. 5. PIN1 joins all availability information, selects the best wavelength. 6. PIN1 sends reserveRequest to the first domain. 7. Hop by hop, each domain marks the slots in database. 8. PIN1 receives the reserveResponse from PIN4. 9. PIN1 returns the reservation ID to the client A.

  28. Interdomain Claim Process PIN1 PIN4 PIN2 PIN3 A B 1. Client A sends a claim request to PIN1 2. Send claimRequest msgs to other domains in parallel. 3. Each domain sets up its part of the lightpath. Then returns success to PIN1 4. PIN1 returns success to the clientA

  29. Signaling Algorithm Complexity Analysis • Reservation • The major time consumed by Reservation process is slot table database access. • pdc-probe: O(hop) • pdc-reserve: O(hop*timeslot) • pin-reserve: O(domain*hop*timeslot) • Claim • The major time consumed is switching time. • Parallelism will help.

  30. RTT: 1ms 60ms 104ms

  31. The Reservation Time is proportional to the Time Slot Granularity

More Related