cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas O'Dowd (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-3028) Object_Store_Refactor - S3 reduced redundancy storage should be an option.
Date Thu, 27 Jun 2013 09:32:19 GMT


Thomas O'Dowd commented on CLOUDSTACK-3028:

The PUT requests no longer ask for REDUCED_REDUNDANCY by default so this looks fixed.

I found the setting under the global settings by doing a search for "s3.". If I change it
do I have to restart the management server or will it automatically start working immediately?

Btw... when I search for "s3." I found 3 options:

1. enable.s3.api ... true
2. s3.enable      ... false
3. s3.rrs.enable ... false

What does the 2nd one do? It seems like S3 is already enabled even though its false??? Is
this a bug - old option or something? I can file another bug for it if you want.

> Object_Store_Refactor - S3 reduced redundancy storage should be an option.
> --------------------------------------------------------------------------
>                 Key: CLOUDSTACK-3028
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Template
>         Environment: latest object_store branch on fedora 17 
> devcloud on same machine 
> Cloudian (for S3 services) on separate machine. (expect similar result with other S3
object stores).
>            Reporter: Thomas O'Dowd
>            Assignee: Min Chen
> When uploading a template to the S3 object store, I noticed that the request asked to
be stored using reduced redundancy. I think this should be an option rather than the default
> Steps: 
> 1. setup S3 object storage (can be amazon) 
> 2. Add S3 as secondary storage 
> 3. Upload a new template (I uploaded "tinyLinux.vhd.gz" by giving a url on my local network
where I had it hosted)
> If you sniff the S3 traffic (assuming you don't use ssl) when you upload the template
in step 3, you can see something like this request.
> =========== initiate multipart upload request ====================
> POST /template%2Ftmpl%2F2%2F201%2F201-2-f9a12429-7cf4-3df5-b81c-420f09c1bbcd%2FtinyLinux.vhd.gz?uploads
> Host:
> Authorization: AWS 00d25034c817eeb8c095:5P8Y2VM69TgAbixlZoXhAsNjAzI=.
> x-amz-storage-class: REDUCED_REDUNDANCY.
> Date: Fri, 14 Jun 2013 07:05:26 GMT.
> User-Agent: aws-sdk-java/ Linux/2.6.32-5-686-bigmem Java_HotSpot(TM)_Client_VM/20.1-b02.
> Content-Type: application/x-www-form-urlencoded; charset=utf-8.
> Transfer-Encoding: chunked.
> Connection: Keep-Alive.
> .
> 0.
> .
> =========== initiate multipart upload request ====================
> Notice that the x-amz-storage-class is set to REDUCED_REDUNDANCY. I cannot see any GUI
option to overload this and choose the default storage class.

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