Re: S3 API broken in 4.2

2013-10-22 Thread Sebastien Goasguen
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

RE: S3 API broken in 4.2

2013-10-22 Thread Sanjeev Neelarapu
: 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

Re: S3 API broken in 4.2

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

Re: S3 API broken in 4.2

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

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 Darren Shepherd
...@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 it so

Re: S3 API broken in 4.2

2013-10-22 Thread Chip Childers
On Tue, Oct 22, 2013 at 2:17 PM, Prachi Damle prachi.da...@citrix.com 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

Re: S3 API broken in 4.2

2013-10-22 Thread Sebastien Goasguen
] 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 it so that the first

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 Darren Shepherd
or updated for a long time and may have many other issues to get it working. Prachi -Original 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

S3 API broken in 4.2

2013-10-21 Thread Darren S
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

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