Opened 5 years ago

Last modified 5 years ago

#1276 new

AL2S OESS aggregate request for specific link capacity is ignored

Reported by: lnevers@bbn.com Owned by: luke@grnoc.iu.edu
Priority: major Milestone:
Component: STITCHING Version: SPIRAL6
Keywords: GENI Network Stitching Cc:
Dependencies:

Description

Requests for specific link capacity are ignored by AL2S OESS aggregate. Regardless of the capacity requested, the link capacity="100000" is always allocated.

Capacity values requests tested:

Requested Capacity Allocated Capacity
20000 100000
200000 100000
100000000(*) 100000

(*) Maximum reservable according to Advertisement RSpec.

Change History (3)

comment:1 Changed 5 years ago by luke@grnoc.iu.edu

AL2S only supports best effort forwarding -- so no matter what link capacity you request, you are always going to get the same thing -- best effort up to your port speed.

How should this be handled in the rspec?

comment:2 in reply to:  1 Changed 5 years ago by lnevers@bbn.com

Replying to luke@…:

AL2S only supports best effort forwarding -- so no matter what link capacity you request, you are always going to get the same thing -- best effort up to your port speed.

How should this be handled in the rspec?

I think that a warning should be reported that the requested capacity is being ignored.

Can this be implemented easily? Or if not, should stitcher be aware of AL2S only supporting best effort forwarding and warn the user?

comment:3 Changed 5 years ago by Aaron Helsinger

Is it possible for AL2S to limit the bandwidth you are given to the requested number?

Does AL2S track capacity it has promised, even if actual capacity is always best effort? If so, it could use that to give errors/warnings that you are going to get best effort.

Note: See TracTickets for help on using tickets.