Unfortunately I'm stuck on 1.6.3. 1.7.x depends on Guava 15.0 and is incompatible with 14.0 (see JCLOUDS-427), but I have to use Guava 14.0 because the version of HBase my company uses (0.94.6) depends on a Guava class that was removed in 15.0.
And yes, I'm using the "s3" provider/API string. So far so good, my test of writing to Ceph was successful! Thanks for your help! *Steve Kingsland* Senior Software Engineer *Opower * <http://www.opower.com/> *We’re hiring! See jobs here <http://www.opower.com/careers> * On Mon, Aug 11, 2014 at 8:26 PM, Andrew Gaul <[email protected]> wrote: > On Mon, Aug 11, 2014 at 08:19:56PM -0400, Steve Kingsland wrote: > > I'm trying to use jclouds' S3 API to connect to an internally-hosted Ceph > > server, which exposes an S3-compliant API. Use other (ruby and perl) > > clients, I've noticed that my requests work fine when I put the > > container/bucket name *after* the hostname, like this: > > > > https://opower.internal/*mybucket/*?acl > > > > However, jclouds is putting the container name *in the hostname* (S3 > calls > > this a "virtual bucket"), like so: > > > > https://*mybucket.*opower.internal/?acl > > > > And that's failing with an "AccessDenied" error that I haven't figured > out > > yet, but am still working on. In the mean time, is there a way to > configure > > jclouds to put the container name *after* the host name, in the request? > > Which version of jclouds do you use? jclouds 1.7.0 should have resolved > this issue: > > https://issues.apache.org/jira/browse/JCLOUDS-305 > > If you use 1.7.0 or newer, can you share the failing operations with > wire logs? Also make sure you use the generic "s3" provider and not the > "aws-s3" specific provider. > > -- > Andrew Gaul > http://gaul.org/ >
