Re: AWS SDK version for object store

2013-07-09 Thread Thomas O'Dowd
I'm +1 also to taking the latest stable release. Tom. On Mon, 2013-07-08 at 13:28 -0400, John Burwell wrote: > Edison, > > I vote to take the latest stable from Amazon. In addition to keeping up with > security and bug fixes, it also ensures that we stay in sync with any > "refinements" that

Re: AWS SDK version for object store

2013-07-08 Thread Chip Childers
riginal Message- >> From: Prasanna Santhanam [mailto:t...@apache.org] >> Sent: 06 July 2013 2:44 PM >> To: dev@cloudstack.apache.org >> Subject: Re: AWS SDK version for object store >> >> On Fri, Jul 05, 2013 at 06:27:46PM +0530, Prasanna Santhanam wrote: >> >

Re: AWS SDK version for object store

2013-07-08 Thread John Burwell
Edison, I vote to take the latest stable from Amazon. In addition to keeping up with security and bug fixes, it also ensures that we stay in sync with any "refinements" that Amazon introduces as part of their continuous improvement/deployment model. Thanks, -John On Jul 8, 2013, at 1:26 PM,

RE: AWS SDK version for object store

2013-07-08 Thread Edison Su
>From CloudStack point of view, there should be minor changes in order to adapt >to latest AWS SDK. What's your guys option, John, Thomas? Is it ok to upgrade >to latest SDK? > -Original Message- > From: Prasanna Santhanam [mailto:t...@apache.org] > Sent: Friday, July 05, 2013 5:58 AM >

RE: AWS SDK version for object store

2013-07-08 Thread Donal Lafferty
also make sure we don't ship something broken. Am I splitting hairs? (http://idioms.thefreedictionary.com/split+hairs) DL > -Original Message- > From: Prasanna Santhanam [mailto:t...@apache.org] > Sent: 06 July 2013 2:44 PM > To: dev@cloudstack.apache.org > Subject

Re: AWS SDK version for object store

2013-07-06 Thread Prasanna Santhanam
On Fri, Jul 05, 2013 at 06:27:46PM +0530, Prasanna Santhanam wrote: > There was another issue I found today with the SDK v1.3.21. It appears > I can't use periods in the name of a bucket. I see an SSL Exception > when this is done [1]. The bug is fixed in the v1.3.22. There are also > couple of oth