Return-Path: X-Original-To: apmail-jclouds-user-archive@minotaur.apache.org Delivered-To: apmail-jclouds-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CB2C418D01 for ; Thu, 3 Dec 2015 01:57:00 +0000 (UTC) Received: (qmail 11720 invoked by uid 500); 3 Dec 2015 01:57:00 -0000 Delivered-To: apmail-jclouds-user-archive@jclouds.apache.org Received: (qmail 11650 invoked by uid 500); 3 Dec 2015 01:57:00 -0000 Mailing-List: contact user-help@jclouds.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@jclouds.apache.org Delivered-To: mailing list user@jclouds.apache.org Received: (qmail 11640 invoked by uid 99); 3 Dec 2015 01:57:00 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Dec 2015 01:57:00 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 2EC401A2128 for ; Thu, 3 Dec 2015 01:57:00 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.149 X-Spam-Level: *** X-Spam-Status: No, score=3.149 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id DeokAORp1Kut for ; Thu, 3 Dec 2015 01:56:51 +0000 (UTC) Received: from mail-qk0-f172.google.com (mail-qk0-f172.google.com [209.85.220.172]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 8CA6B30E17 for ; Thu, 3 Dec 2015 01:56:51 +0000 (UTC) Received: by qkfo3 with SMTP id o3so24591871qkf.1 for ; Wed, 02 Dec 2015 17:56:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=MuurLX9bbGtSfmlJPNSLwIN0oj72PfH8a9ezpqQ8KhQ=; b=LoRNTmtb7UhqUGeGoSe4L6a6wOryoWyKuPGDN5tb5OTB7tOz6Up8nC5v/Hxbk/85xN 4rrLYXkrTSAXk3a9+AcKw4PM0/hfcaCoW9TPkSXBJpIcJpy7E76X8Z1cFbZ0SE0a0xny 77DwuF5WlPdepubmthZ/XWfVyViX06liIQwfy4zFMvJs+Z7gc83hfZqY3NHUOeI7NDTw Yox9XdIDOMU20iANXcUhi2lf147SXFSrorGXsTo9+erOrZ6KRKiPm00ixd4pXdplZPG1 PjJ+Xucuz4eGFnXRcDnhlcXFwI5y0UzrztgfIi7ssZL78Kslpk14Qb3bjagPJuMPqnHk umvw== X-Received: by 10.55.72.23 with SMTP id v23mr7906182qka.24.1449107810514; Wed, 02 Dec 2015 17:56:50 -0800 (PST) MIME-Version: 1.0 References: <3faa22f7f18388b8ae88721216398a6e@qrmedia.com> In-Reply-To: From: Forrest Townsend Date: Thu, 03 Dec 2015 01:56:41 +0000 Message-ID: Subject: Re: jclouds 1.8.1 to Openstack Swift3 object store To: Andrew Phillips Cc: user@jclouds.apache.org Content-Type: multipart/alternative; boundary=001a114a8ae249979f0525f4b41a --001a114a8ae249979f0525f4b41a Content-Type: text/plain; charset=UTF-8 Hi, Thanks for the quick response. Am able to get the bucket's acl using the boto3 library. I could get you the acl output if you would like, if you think that would be any helpful.. Could this be related to the fact that I'm using the 's3' builder versus the 'aws-s3'? Thanks, Forrest T. On Wed, Dec 2, 2015, 6:13 PM Andrew Phillips wrote: > Hi Forrest > > Thanks for the update! > > > Where it looks like I fail is when I am doing a GET > > request on this, http://:8080/?acl, more > > than once and eventually getting an Internal Server Error -- > > > > 2015-12-02 17:06:31.095 DEBUG [Thread-12] j.headers >> GET > > > http://vcloud210.storage.tucson.ibm.com:8080/418-b7ff7d008a2711e5bbb9080027001c70?acl > > From your code snippets, I would guess that the ACL calls are coming > from the putBlob call, since createContainerInLocation for the S3 API > [1] resolves more or less to a straight putBucketInRegion call [2], > whereas putBlob includes a call to get the bucket's ACL [3]. > > Having said that, the getBucketACL call [4] is a call that, according to > these OpenStack docs [5], is "known to be supported". If that call is > actually blowing up for some reason, that would initially seem to point > towards a bug on the OpenStack side. > > Are you able to make a successful call to get the bucket's ACL with cURL > or similar, or do you get the same error? > > Regards > > ap > > [1] > > https://github.com/jclouds/jclouds/blob/master/apis/s3/src/main/java/org/jclouds/s3/S3Client.java > [2] > > https://github.com/jclouds/jclouds/blob/master/apis/s3/src/main/java/org/jclouds/s3/blobstore/S3BlobStore.java#L433 > [3] > > https://github.com/jclouds/jclouds/blob/master/apis/s3/src/main/java/org/jclouds/s3/blobstore/S3BlobStore.java#L277 > [4] > > https://jclouds.apache.org/reference/javadoc/1.8.x/org/jclouds/s3/S3Client.html#getBucketACL(java.lang.String) > [5] https://wiki.openstack.org/wiki/Swift/APIFeatureComparison > --001a114a8ae249979f0525f4b41a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hi,

Thanks for the quick response.

Am able to get the bucket's acl using the boto3 library.=

I could get you the acl output if you would like, if you thi= nk that would be any helpful..

Could this be related to the fact that I'm using the = 9;s3' builder versus the 'aws-s3'?

Thanks,
Forrest T.


On Wed, Dec 2, 2015, 6:13 P= M=C2=A0Andrew Phillips <andrewp@ap= ache.org> wrote:
Hi Forrest<= br>
Thanks for the update!

> Where it looks like I fail is when I am doing a GET
> request on this, http://<url>:8080/<bucket_name>?acl, more=
> than once and eventually getting an Internal Server Error --
>
> 2015-12-02 17:06:31.095 DEBUG [Thread-12] j.headers >> GET
> http://vcl= oud210.storage.tucson.ibm.com:8080/418-b7ff7d008a2711e5bbb9080027001c70?acl=

=C2=A0From your code snippets, I would guess that the ACL calls are coming<= br> from the putBlob call, since createContainerInLocation for the S3 API
[1] resolves more or less to a straight putBucketInRegion call [2],
whereas putBlob includes a call to get the bucket's ACL [3].

Having said that, the getBucketACL call [4] is a call that, according to these OpenStack docs [5], is "known to be supported". If that cal= l is
actually blowing up for some reason, that would initially seem to point
towards a bug on the OpenStack side.

Are you able to make a successful call to get the bucket's ACL with cUR= L
or similar, or do you get the same error?

Regards

ap

[1]
htt= ps://github.com/jclouds/jclouds/blob/master/apis/s3/src/main/java/org/jclou= ds/s3/S3Client.java
[2]
https://github.com/jclouds/jclouds/blob/master/apis/s3/src/m= ain/java/org/jclouds/s3/blobstore/S3BlobStore.java#L433
[3]
https://github.com/jclouds/jclouds/blob/master/apis/s3/src/m= ain/java/org/jclouds/s3/blobstore/S3BlobStore.java#L277
[4]
https://jclouds.apache.org/reference/javadoc/1.8.x/org/jclouds/= s3/S3Client.html#getBucketACL(java.lang.String)
[5] https://wiki.openstack.org/wiki/Swift/= APIFeatureComparison
--001a114a8ae249979f0525f4b41a--