Limit Volume Copy Bandwidth Per Backend

Registered by Tomoki Sekiyama on 2014-07-10

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:
milestone icon 2015.1.0
Started by
Tomoki Sekiyama on 2015-02-04
Completed by
Mike Perez on 2015-03-02

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/limit-volume-copy-bps-per-backend,n,z

Addressed by: https://review.openstack.org/106187
    Limit Volume Copy Bandwidth Per Backend

Gerrit topic: https://review.openstack.org/#q,topic:bp/s,n,z

Addressed by: https://review.openstack.org/149446
    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.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.