Yes, it's still a same behavior and maybe this is by design. So now this bug is confusing. An actual problem that I'm now seeing is that if copy-from is used and s3 is used for storage and its size is big(>100M), the multi-part upload will be used.(I'm now backporting this feature to glance_store in 120714) However it will be always done per the chunk_size which is 64k. That is the problem. Because each part must be at least 5 MB in size in Amazon S3.(http://docs.aws.amazon.com/AmazonS3/latest/API/mpUploadUploadPart.html) So eventually the operation will fail. I think it's better to file a new BUG for this and close this BUG.
Yes, it's still a same behavior and maybe this is by design. So now this bug is confusing. An actual problem that I'm now seeing is that if copy-from is used and s3 is used for storage and its size is big(>100M), the multi-part upload will be used.(I'm now backporting this feature to glance_store in 120714) However it will be always done per the chunk_size which is 64k. That is the problem. Because each part must be at least 5 MB in size in Amazon S3.(http:// docs.aws. amazon. com/AmazonS3/ latest/ API/mpUploadUpl oadPart. html) So eventually the operation will fail. I think it's better to file a new BUG for this and close this BUG.
[Implemented S3 multi-part upload functionality] /review. openstack. org/#/c/ 49316/
https:/
[Backporting S3 multi-part upload functionality to glace_store] /review. openstack. org/#/c/ 120714/
https:/