cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanjeev Neelarapu <sanjeev.neelar...@citrix.com>
Subject RE: S3 API broken in 4.2
Date Tue, 22 Oct 2013 12:14:00 GMT
Hi Darren,

>From 4.2 onwards we are using addImageStore API with provider parameter for adding any
secondary storage provider.

-Sanjeev

-----Original Message-----
From: Sebastien Goasguen [mailto:runseb@gmail.com] 
Sent: Tuesday, October 22, 2013 2:44 PM
To: dev@cloudstack.apache.org
Subject: Re: S3 API broken in 4.2


On Oct 22, 2013, at 1:22 AM, Chiradeep Vittal <Chiradeep.Vittal@citrix.com> wrote:

> Yeah, it was always a tech preview kind of thing. The basic operations 
> used to work, but since most of the available client tools
> (s3cmd/boto/etc) had special workarounds for odd AWS behaviors (in the 
> return behavior), they would have a hard time working with the S3 
> implementation in CloudStack which was based entirely on the WSDL.

Shall we remove it ? to clean up the code

Especially that it is easy to get an S3 store with riakCS, gluster or ceph radosgw.


> 
> On 10/21/13 10:16 PM, "Darren S" <darren.s.shepherd@gmail.com> wrote:
> 
>> I didn't even know this feature existed until yesterday, so I thought 
>> I'd try it out, but it seems that the S3 API in CloudStack completely 
>> doesn't work in 4.2.  Is it supposed to?  Is this an official feature 
>> or some tech preview type thing?
>> 
>> Darren
> 


Mime
View raw message