, Julie
Subject: Re: Use JClouds to talk to non AWS cloud with S3 API
We did face a similar issue in the past, and found that the accept header set
by the HttpClient was being rejected by the Swift3 middleware. We replaced it
with apache httpclient, and it worked. Perhaps you could give it a try
nal Message-
From: Andrew Phillips [mailto:andr...@apache.org]
Sent: Sunday, January 31, 2016 1:35 PM
To: user@jclouds.apache.org
Subject: RE: Use JClouds to talk to non AWS cloud with S3 API
Hm...not much difference there:
s3curl call that succeeds:
HEAD /public HTTP/1.1
User-Agent: curl/7.15.5 (x8
Hm...not much difference there:
s3curl call that succeeds:
HEAD /public HTTP/1.1
User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5
OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5
Host: jag-itop-svr.dev.opsware.com:8080
Accept: */*
Date: Sun, 31 Jan 2016 17:54:30 +
Authorization: AWS
ailto:andr...@apache.org]
Sent: Sunday, January 31, 2016 12:27 PM
To: Yao, Julie
Cc: user@jclouds.apache.org
Subject: RE: Use JClouds to talk to non AWS cloud with S3 API
Hi Julie
Thanks for the additional details! Good to see we're now trying to connect to
the same URL in both cases (i.e.
ontainerExists(bucket);
I also have VM args:
-Djclouds.trust-all-certs=true -Djclouds.relax-hostname=true
-Djclouds.provider=s3
Thanks!
-Original Message-
From: Yao, Julie
Sent: Sunday, January 31, 2016 10:01 AM
To: Andrew Phillips; user@jclouds.apache.org
Subject: RE: Use JClouds to talk
der=s3
Thanks!
-Original Message-
From: Yao, Julie
Sent: Sunday, January 31, 2016 10:01 AM
To: Andrew Phillips; user@jclouds.apache.org
Subject: RE: Use JClouds to talk to non AWS cloud with S3 API
> Ah, OK. To confirm: are we calling a Walrus installation here?
No
I got s3curl.pl workin
dr...@apache.org]
Sent: Friday, January 29, 2016 6:35 PM
To: user@jclouds.apache.org
Cc: Yao, Julie
Subject: RE: Use JClouds to talk to non AWS cloud with S3 API
> I guess
> overrides.setProperty(PROPERTY_S3_SERVICE_PATH, "/services/Walrus");
> is not correct.
> Without it
I guess
overrides.setProperty(PROPERTY_S3_SERVICE_PATH, "/services/Walrus");
is not correct.
Without it, it will throw exception.
Ah, OK. To confirm: are we calling a Walrus installation here?
Also, in your boto code snippet:
def connect(self):
self.connection = boto.connect_s3 (
I attach log here.
Looking at the logs, I don't think the
overrides.setProperty(PROPERTY_S3_SERVICE_PATH, "/services/Walrus");
setting is correct :-( The logs show that jclouds is trying to call
2016-01-29 16:27:24,495 DEBUG [jclouds.headers] [main] >> PUT
http://jag-itop-svr.dev.opsware.com
I tried S3Client and the result is still wrong.
Is that the right code snippet? The example you included still uses the
portable BlobStore interface?
Regards
ap
]
Sent: Friday, January 29, 2016 3:23 PM
To: user@jclouds.apache.org
Cc: Yao, Julie
Subject: RE: Use JClouds to talk to non AWS cloud with S3 API
> but the result is wrong.
Ah, pity :-( Caught celebrating too soon ;-) One of the things that may be
worth trying here is to move away from the portably blo
but the result is wrong.
Ah, pity :-( Caught celebrating too soon ;-) One of the things that may
be worth trying here is to move away from the portably blobstore
abstraction and try the API directly - that's more comparable to the
boto calls.
...
S3Client client = ContextBuilder.newBuilder(
inerInLocation(S3BlobStore.java:143)
at com.itoa.server.test.RepositoryS3.main(RepositoryS3.java:41)
Thanks!
-Original Message-----
From: Yao, Julie
Sent: Friday, January 29, 2016 11:53 AM
To: user@jclouds.apache.org
Subject: RE: Use JClouds to talk to non AWS cloud with S
Thanks for the heads-up, Julie - glad you were able to get it to work!
ap
ssage-
From: Yao, Julie
Sent: Friday, January 29, 2016 10:49 AM
To: user@jclouds.apache.org
Subject: RE: Use JClouds to talk to non AWS cloud with S3 API
Code snippet using boto:
def connect(self):
self.connection = boto.connect_s3 (
aws_access_key_id
positoryS3.main(RepositoryS3.java:32)
Thanks!
-Original Message-
From: Andrew Phillips [mailto:andr...@apache.org]
Sent: Thursday, January 28, 2016 9:05 PM
To: user@jclouds.apache.org
Cc: Yao, Julie
Subject: Re: Use JClouds to talk to non AWS cloud with S3 API
Hi Julie
Could you enabl
We did face a similar issue in the past, and found that the accept header
set by the HttpClient was being rejected by the Swift3 middleware. We
replaced it with apache httpclient, and it worked. Perhaps you could give
it a try.
Iterable modules = ImmutableSet. of(new
ApacheHCHttpComma
Hi Julie
Could you enable wire and debug logging so we can see exactly which
calls jclouds is making [1]? Also, could you share a code snippet of how
you are successfully using boto to do the same thing? Hopefully, we can
find out where the calls from jclouds differ from what boto is doing...
I am using jcloud 1.9.2. We have set up our own swift repository with s3 api.
We can access the repository using boto python script
I am using the code in the following post
http://stackoverflow.com/questions/9389840/use-jclouds-to-talk-to-non-aws-cloud-with-s3-api
but I got error.:
public
19 matches
Mail list logo
