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:
>>>
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:[email protected]]
Sent: Tuesday, October 22, 2013 11:29 AM
To: [email protected]
Subject: Re: S3 API broken in 4.2
On Tue
riginal Message-
>> From: Darren Shepherd [mailto:[email protected]]
>> Sent: Tuesday, October 22, 2013 11:06 AM
>> To: [email protected]
>> Subject: Re: S3 API broken in 4.2
>>
>> The S3 servlet never initializes. A NPE is thrown in the init(
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
lto:[email protected]]
> Sent: Tuesday, October 22, 2013 11:06 AM
> To: [email protected]
> 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
[mailto:[email protected]]
Sent: Tuesday, October 22, 2013 11:06 AM
To: [email protected]
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
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:[email protected]]
>
>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:[email protected]]
>>Sen
gt;-Sanjeev
>
>-Original Message-
>From: Sebastien Goasguen [mailto:[email protected]]
>Sent: Tuesday, October 22, 2013 2:44 PM
>To: [email protected]
>Subject: Re: S3 API broken in 4.2
>
>
>On Oct 22, 2013, at 1:22 AM, Chiradeep Vittal
> wrote:
>
&
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
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
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
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
13 matches
Mail list logo
