All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Benjamin <mbenjami@redhat.com>
To: "Zhou, Yuan" <yuan.zhou@intel.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: RGW S3 vs S3 signature
Date: Thu, 18 Jan 2018 09:53:03 -0500	[thread overview]
Message-ID: <CAKOnarkJS2GX-SU4yiBcdRD7TNpcAcjx1kbDEypamJY-eqzmWw@mail.gmail.com> (raw)
In-Reply-To: <06681238D8946F44A60AA400760A1CBF124E0505@SHSMSX103.ccr.corp.intel.com>

Hi Yuan,

AWS v4 signatures are supported in Jewel.  Could you create a tracker
issue with RGW debug logs to help track down the issue you hit?

thanks,

Matt

On Thu, Jan 18, 2018 at 9:39 AM, Zhou, Yuan <yuan.zhou@intel.com> wrote:
> Hello,
>
> Trying to some tests with Hadoop 2.9 + Ceph S3(Jewel, 10.2.10) and ran into a multi-part uploading issue. It looks like the new S3a driver(aws-java-sdk-bundle-1.11.199.jar, v4 signature) in Hadoop is not compatible with Ceph S3(Jewel).
>
> I find there's a doc on S3 API support status, but lack of the corresponding S3 version info there. Is there any info on the detail supported version, v2 only?
> http://docs.ceph.com/docs/jewel/radosgw/s3/
>
> I also find some commit to enable the V4 support here, I think this should be ready in Luminous?
> https://github.com/ceph/ceph/pull/15965/commits/82a7aa9e3eabfde4a82046d78aad2dadbfc0d8e1
>
>
> Any comments would be appreciated!
>
> Thanks, -yuan
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 

Matt Benjamin
Red Hat, Inc.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103

http://www.redhat.com/en/technologies/storage

tel.  734-821-5101
fax.  734-769-8938
cel.  734-216-5309

      reply	other threads:[~2018-01-18 14:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 14:39 RGW S3 vs S3 signature Zhou, Yuan
2018-01-18 14:53 ` Matt Benjamin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKOnarkJS2GX-SU4yiBcdRD7TNpcAcjx1kbDEypamJY-eqzmWw@mail.gmail.com \
    --to=mbenjami@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=yuan.zhou@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.