Transfer Rate Limiting

Registered by John Bresnahan on 2013-02-12

Adding quotas to glance would enable admins to better manage their resources. The blue print here: https://blueprints.launchpad.net/glance/+spec/glance-basic-quotas begins to address this. The thought of having a common service for handling various user quota throughout OpenStack is addressed here: https://blueprints.launchpad.net/nova/+spec/ledger-quota-subsystem. This is a welcome idea and this blue print does not go against it. One of the resources that needs a quota is the image transfer speeds. While determining the limit for any given image transfer could be determined by such a central service, enforcement of the rate limiting will need to be local to glance (because a network API call for every buffer sent would be too damaging to performance). This blueprint proposes that we add transfer rate limiting inside of glance. Until a quota service is created the limit will be obtained via a configuration option. Once the service exists it should be trivial to replace the configuration option with a call out to a quota service.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
John Bresnahan
Direction:
Needs approval
Assignee:
John Bresnahan
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
John Bresnahan on 2013-07-19

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/transfer-rate-limiting,n,z

Addressed by: https://review.openstack.org/21380
    Download rate limiting

It looks like consensus during summit discussion that rate limiting should be a separate facility running as a proxy in front of glance.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.