cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4816) provide configurable option to choose single vs multipart upload to S3 object storage
Date Sat, 26 Oct 2013 05:50:30 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806009#comment-13806009
] 

ASF subversion and git services commented on CLOUDSTACK-4816:
-------------------------------------------------------------

Commit 2c0534794e1c9648241dc6f5e5cebac7852d4ed2 in branch refs/heads/object_store_migration
from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2c05347 ]

CLOUDSTACK-4816: Removed unused field from S3TO to avoid confusion in
the log.


> provide configurable option to choose single vs multipart upload to S3 object storage

> --------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4816
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4816
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller
>    Affects Versions: 4.2.0
>            Reporter: Min Chen
>            Assignee: Min Chen
>            Priority: Critical
>             Fix For: 4.2.1
>
>
> In 4.2, we only supports multipart upload for registering templates and uploading volumes
to object storage in secondary storage. The value of multi-part is for network failure and
throughput when you are going to a remote storage. But with local storage (local to the DC)
customers may prefer single upload. Also, for templates you know the full size of the object
upfront and don't really need a multipart upload.
> Some object storage vendors may prefer that this can be configured.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message