Backlog #665
Allow rate limiting of a VIF.
Status: | Closed | Start date: | 05/26/2011 | |
---|---|---|---|---|
Priority: | High | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Core & System | |||
Target version: | - |
Description
Xen allows one to set an upload rate limit on a virtual interface. I am interesting in leveraging this functionnality through Open Nebula.
The way I see it, a VIF could take an optional parameter called "RATE". If such a rate is specified, it would then be passed onto the deployment file.
I do not know if KVM supports such an option.
Related issues
History
#1 Updated by Vivien Bernet-Rollande about 10 years ago
- File one_xen_rate_limit.diff added
The attached patch allows one to limit the upload network rate for a NIC.
#2 Updated by Ruben S. Montero almost 10 years ago
- Status changed from New to Closed
- Resolution set to duplicate
#3 Updated by Ruben S. Montero over 9 years ago
- Status changed from Closed to New
- Resolution deleted (
duplicate)
Ups it seems that we mark both as duplicate.... Re-opening this
#4 Updated by Ruben S. Montero about 8 years ago
- Tracker changed from Feature to Request
#5 Updated by Ruben S. Montero about 8 years ago
- Priority changed from Normal to Low
#6 Updated by Ruben S. Montero about 8 years ago
- Tracker changed from Request to Backlog
#7 Updated by Ruben S. Montero about 8 years ago
- Status changed from New to Pending
#8 Updated by Simon Boulet about 8 years ago
RATE can be ambiguous because in some cases one might also want to limit the number of packets per second, or perhaps specify an inbound limit (which could be different than outbound). I'm thinking something like: RATE_BPS_IN, RATE_BPS_OUT, RATE_PPS_IN, RATE_PPS_OUT.
#9 Updated by Ruben S. Montero over 7 years ago
- Assignee deleted (
Vivien Bernet-Rollande) - Priority changed from Low to High
#10 Updated by Ruben S. Montero over 7 years ago
- Related to Backlog #2531: Add support for DISK/RAW and NIC/RAW added
#11 Updated by Ruben S. Montero almost 7 years ago
- Related to Feature #3045: Network qos support added
#12 Updated by Ruben S. Montero over 6 years ago
- Target version set to Release 4.14
#13 Updated by Ruben S. Montero over 6 years ago
- Tracker changed from Backlog to Feature
#14 Updated by Ruben S. Montero over 6 years ago
- Status changed from Pending to New
#15 Updated by Ruben S. Montero about 6 years ago
- Tracker changed from Feature to Backlog
- Target version changed from Release 4.14 to Release 5.0
#16 Updated by Ruben S. Montero over 5 years ago
- Status changed from New to Pending
- Target version deleted (
Release 5.0)
#17 Updated by Ruben S. Montero almost 4 years ago
- Status changed from Pending to Closed