Darren, can you be specific what exact s3 API is not working in 4.2? Thanks -min
On 10/22/13 5:14 AM, "Sanjeev Neelarapu" <sanjeev.neelar...@citrix.com> wrote: >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:run...@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.vit...@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.sheph...@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 >> >
