Limit Volume Copy Bandwidth Per Backend
Currently, cinder has a global configuration to limit a volume copy bandwidth to mitigate slow down of instances volume access during large image copies.
This spec proposes to make this config variable per backend.
Blueprint information
- Status:
- Complete
- Approver:
- Mike Perez
- Priority:
- Medium
- Drafter:
- Tomoki Sekiyama
- Direction:
- Approved
- Assignee:
- Tomoki Sekiyama
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
-
Implemented
- Milestone target:
-
2015.1.0
- Started by
- Tomoki Sekiyama
- Completed by
- Mike Perez
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Limit Volume Copy Bandwidth Per Backend
Gerrit topic: https:/
Addressed by: https:/
Limit volume copy bandwidth per backend
You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(This is an automated message)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
