Re: S3 API broken in 4.2

2013-10-22 Thread Darren Shepherd
en wrote: >>>> 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" >>>> >>>> wrote: >>>

RE: S3 API broken in 4.2

2013-10-22 Thread Prachi Damle
We can remove the S3 source in 4.3, wonder if we know of any users using the tech preview version. -Original Message- From: Chip Childers [mailto:chipchild...@apache.org] Sent: Tuesday, October 22, 2013 11:29 AM To: dev@cloudstack.apache.org Subject: Re: S3 API broken in 4.2 On Tue

Re: S3 API broken in 4.2

2013-10-22 Thread Sebastien Goasguen
riginal Message- >> From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com] >> Sent: Tuesday, October 22, 2013 11:06 AM >> To: dev@cloudstack.apache.org >> Subject: Re: S3 API broken in 4.2 >> >> The S3 servlet never initializes. A NPE is thrown in the init(

Re: S3 API broken in 4.2

2013-10-22 Thread Chip Childers
On Tue, Oct 22, 2013 at 2:17 PM, Prachi Damle wrote: > Yes, either moving the line to constructor or using a local SearchBuilder > will fix it - however the S3 APIs part in awsapi project is not supported or > updated for a long time and may have many other issues to get it working. > > Prachi

Re: S3 API broken in 4.2

2013-10-22 Thread Darren Shepherd
lto:darren.s.sheph...@gmail.com] > Sent: Tuesday, October 22, 2013 11:06 AM > To: dev@cloudstack.apache.org > Subject: Re: S3 API broken in 4.2 > > The S3 servlet never initializes. A NPE is thrown in the init() method. > Basically there is a silly bug in > CloudStackConfiguratio

RE: S3 API broken in 4.2

2013-10-22 Thread Prachi Damle
[mailto:darren.s.sheph...@gmail.com] Sent: Tuesday, October 22, 2013 11:06 AM To: dev@cloudstack.apache.org Subject: Re: S3 API broken in 4.2 The S3 servlet never initializes. A NPE is thrown in the init() method. Basically there is a silly bug in CloudStackConfigurationDaoImpl.getConfigValue() that makes

Re: S3 API broken in 4.2

2013-10-22 Thread Min Chen
t;> >> >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] >

Re: S3 API broken in 4.2

2013-10-22 Thread Darren Shepherd
>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] >>Sen

Re: S3 API broken in 4.2

2013-10-22 Thread Min Chen
gt;-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 > wrote: > &

RE: S3 API broken in 4.2

2013-10-22 Thread Sanjeev Neelarapu
ubject: Re: S3 API broken in 4.2 On Oct 22, 2013, at 1:22 AM, Chiradeep Vittal 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 be

Re: S3 API broken in 4.2

2013-10-22 Thread Sebastien Goasguen
On Oct 22, 2013, at 1:22 AM, Chiradeep Vittal 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

Re: S3 API broken in 4.2

2013-10-21 Thread Chiradeep Vittal
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 whi