Opened 12 years ago
Closed 12 years ago
#1017 closed (fixed)
Enforce capacity restrictions on requests
| Reported by: | Aaron Helsinger | Owned by: | xyang@maxgigapop.net |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | I2AM | Version: | SPIRAL5 |
| Keywords: | Cc: | tlehman@maxgigapop.net, Aaron Helsinger, ckotil@grnoc.iu.edu | |
| Dependencies: |
Description
The ION AM should
- ensure capacity is available as requested for each hop/link in the stitching extension (using the capacity property in the link if not supplied in the stitching extension)
- ensure compliance of the request with the capacity elements in the Ad (maximumReservableCapacity, minimumReservableCapacity, and granularity)
- pass along the capacity requested to the ION service
Change History (2)
comment:1 Changed 12 years ago by
| Status: | new → assigned |
|---|
comment:2 Changed 12 years ago by
| Cc: | Aaron Helsinger ckotil@grnoc.iu.edu added |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
Code checked in.
Chad, please update the ION AM. Also modify the stitch topology file to use kbps as default unit ==> %s/1000000/1000/g.
Note: See
TracTickets for help on using
tickets.
ION AM does not ensure the capacity is available as the actual capacity varies due to dynamic allocations that the AM is not aware of. Solution to this ticket only ensures the capacity is conforming (multiple of granularity between maximumReservableCapacity and minimumReservableCapacity)