cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanna Santhanam (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-3275) Object_Store : Provide a mechanism to track multipart image upload progress
Date Fri, 28 Jun 2013 13:25:20 GMT
Prasanna Santhanam created CLOUDSTACK-3275:

             Summary: Object_Store : Provide a mechanism to track multipart image upload progress
                 Key: CLOUDSTACK-3275
             Project: CloudStack
          Issue Type: Improvement
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Storage Controller
    Affects Versions: 4.2.0
            Reporter: Prasanna Santhanam
             Fix For: Future

This would be nice to track the progress of the downloads to an image store similar to how
the DownloadProgressCommand used to work for secondary store backed by NFS.

On IRC you asked the following question but quit before I could answer:

        tpodowd: it's a problem not to be able to see the progress of
        the download. does s3 have a mechanism to provide callback for

yes and no...

For uploads you can do it by splitting your upload into parts and doing
a multipart upload. Right now, its using 5M parts so after each 5M part
is uploaded you could update progress. You probably know how many 5M
parts you'll upload so % is easy.

For downloads objects can be either small or huge. There is no concept
of downloading parts per-say but you could download using the Range
header... Ie, you can request the 1st 5M of an object in your first GET,
the next 5M in the 2nd GET etc until you have all the object. In this
way you can also download in parallel and report progress after each get
completes. You know the size of the object because you can do a HEAD on
it so a % is also do-able.

So yes it's possible both ways but perhaps more hassle.

Hope that helps.


This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message