From: Abhishek Lekshmanan <abhishek@suse.com>
To: Andreas Calminder <andreas.calminder@klarna.com>,
Matt Benjamin <mbenjami@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: RGW bucket tagging
Date: Mon, 29 Jan 2018 11:04:47 +0100 [thread overview]
Message-ID: <87inblou9s.fsf@suse.com> (raw)
In-Reply-To: <CAA1GxO2CbG=UR_4SKb4pV-j78ZG-nzjwaD+veqgx-RyQBryOSg@mail.gmail.com>
Andreas Calminder <andreas.calminder@klarna.com> writes:
> Thanks for your reply Matt, I did some more poking around; you're
> right, there's no support for bucket tagging. Does anyone know if this
> feature will be implemented somewhere in the foreseeable future?
Yeah, this feature isn't implemented yet.
Though it should be relatively easier to implement, since it doesn't tie
into any other functionalities unlike object tagging, and purely
provides a tagging API which is similar to what we've already
implemented for Object Tagging.
>
> Best regards,
> andreas
>
> On 26 January 2018 at 17:08, Matt Benjamin <mbenjami@redhat.com> wrote:
>> Hi Andreas,
>>
>> I think we don't support bucket tagging yet. There is support for
>> object tagging, plus integration w/bucket policy and lifecycle.
>>
>> Abhishek, do you have anything to add here?
>>
>> Matt
>>
>> On Fri, Jan 26, 2018 at 9:47 AM, Andreas Calminder
>> <andreas.calminder@klarna.com> wrote:
>>> Hello,
>>> I'm evaluating the possibility of using tags for buckets in RGW, using
>>> boto3 s3.BucketTagging.put returns client error and the rgw log
>>> throws a 400 and says: provided input did not specify location
>>> constraint correctly
This ideally should've reported 501 NotImplemented instead of a client
error (probably still does for AWSv4 auth?)
>>>
>>> I figured it's most likely that I did something silly in the code,
>>> however before digging deeper I figured I should probably check if
>>> it's even supported in RGW, I found this:
>>> http://docs.ceph.com/docs/master/dev/radosgw/s3_compliance/
>>>
>>> Which says Bucket Tagging "?", So I suspect Bucket Tagging isn't
>>> supported? Any clarification or pointers appreciated here.
>>>
>>> Thanks!
>>> --
>>> 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
>
--
Abhishek Lekshmanan
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
prev parent reply other threads:[~2018-01-29 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 14:47 RGW bucket tagging Andreas Calminder
2018-01-26 16:08 ` Matt Benjamin
2018-01-29 7:25 ` Andreas Calminder
2018-01-29 7:41 ` Robin H. Johnson
2018-01-29 10:04 ` Abhishek Lekshmanan [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=87inblou9s.fsf@suse.com \
--to=abhishek@suse.com \
--cc=andreas.calminder@klarna.com \
--cc=ceph-devel@vger.kernel.org \
--cc=mbenjami@redhat.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.