Bug 1041767 - [RFE][glance]: we should retry swift auth for each chunk upload
Summary: [RFE][glance]: we should retry swift auth for each chunk upload
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/glan...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 19:14 UTC by RHOS Integration
Modified: 2015-11-20 19:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:28:07 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 19:14:26 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/retry-auth-swift-uploads.

Description:

Currently, if we want to upload a large image file from glance to swift and the auth token is about to expire, it will result into 401. However, if we fetch a new token for each chunk we upload it would be a much safer choice. There can be some optimizations here like:
- we look for the expiration time within the eventlet thread and recreate a new token when the old one is about to expire
We can cache the token if needed and set the expiry time in the cache. 
 - Or, we can try to have a Retryable error raised within the exception and that way either a new thread can be spun up for uploading the remnant chunks.

Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.