Re: Client debugging and rados_conf_set()

On Tue, 24 Feb 2015 21:36:07 -0800 (PST) Sage Weil s...@newdream.net wrote: ldout(cct, 1) setting wanted keys dendl; rc = rados_conf_set(rados, debug_rados, 20/20); rados_conf_set(rados, log_to_stderr, true); Thanks a lot, that worked! -- Pete -- To unsubscribe from this list:

Client debugging and rados_conf_set()

Hello: I noticed that RadosClient.cc is full of interesting printouts, like so: ldout(cct, 1) setting wanted keys dendl; So, I tried to enable them by doing this: rc = rados_conf_set(rados, debug_rados, 20/20); However, the above produces no output. What am I missing? How are

What is omap

Dear All: I am a complete beginner in Ceph and due to various circumstances I became curious about omap. I made some quick web searches and read some random writings about it, but I still have basic questions. - If I had to refer to omap in a doc/foo.rst, is there a canonical web-page, blog

Re: xattrs vs. omap with radosgw

On Tue, 16 Jun 2015 12:43:08 -0700 (PDT) Sage Weil s...@newdream.net wrote: With hammer the size of object_info_t crossed the 255 byte boundary, which is the max xattr value that XFS can inline. We've since merged something that stripes over several small xattrs so that we can keep things

Re: What is omap

On Fri, 26 Jun 2015 14:48:15 +0100 Gregory Farnum g...@gregs42.com wrote: Each object consists of three different data storage areas, all of which are 100% optional: the bundle of bits object data, the object xattrs, and the object omap key-value store. Thanks for the explanation. This was

Civetweb and mg_set_http_status

I did a git pull today and now the build breaks like this: CXX rgw/libcivetweb_la-rgw_civetweb.lo rgw/rgw_civetweb.cc: In member function 'virtual int RGWMongoose::send_status(const char*, const char*)': rgw/rgw_civetweb.cc:147:38: error: 'mg_set_http_status' was not declared in this

RGWUserInfo encode/decode

Hi, I stumpbled upon a code like this in src/rgw/rgw_common.h: struct RGWUserInfo { mapstring, RGWAccessKey swift_keys; // not one swift_key, a whole map void decode(bufferlist::iterator bl) { string swift_key; if (struct_v = 4) ::decode(swift_key, bl); // that's all, folks }

Re: Moving away from Yum/DNF repo priorities for Ceph and ceph-deploy

On Thu, 23 Jul 2015 16:12:59 -0700 Travis Rhoden trho...@redhat.com wrote: I’m working on ways to improve Ceph installation with ceph-deploy, and a common hurdle we have hit involves dependency issues between ceph.com hosted RPM repos, and packages within EPEL. For a while we were able to

RGW multi-tenancy APIs overview

With ticket 5073 getting close to complete, we're getting the APIs mostly nailed down. Most of them come down to selection a syntax separator character. Unfortunately, there are several such characters. Plus, it is not always feasible to get by with a character (in S3 at least). So far we have

Re: Bucket namespaces pull req. 5872

On Mon, 26 Oct 2015 16:09:41 +0100 Radoslaw Zarzynski wrote: > Those are the reasons I’m behind keeping rgw_user even if the > entire information it carries would be solely an ID string. Okay. It felt a little obfuscatory but perhaps it's my kernel background talking.

Re: Symbolic links like feature on radosgw

On Mon, 2 Nov 2015 21:25:31 -0800 Guang Yang wrote: > Is this a valid feature request we can put into radosgw? The way I am > thinking to implement is like symbolic link, the link object just > contains a pointer to the original object. It's not going to be sufficient. What

Bucket namespaces pull req. 5872

I took a decent look at the pull request 5872 https://github.com/ceph/ceph/pull/5872 It implements something called "bucket namespaces": a way to make buckets qualified with a prefix that permits different users use buckets with the same name. I think I like the idea overall, but the

Re: RGW multi-tenancy APIs overview

On Mon, 9 Nov 2015 21:36:47 -0800 Yehuda Sadeh-Weinraub wrote: We discussed this a bit on RGW team meeting in BJ, and there were some developments, so for the sake of update here goes. > > #1 Back-end and radosgw-admin use '/' or "tenant/bucket". This is what is > > literally

Re: RGW multi-tenancy APIs overview

On Tue, 17 Nov 2015 16:00:12 -0800 Yehuda Sadeh-Weinraub wrote: > > http://s3.amazonaws.com/doc/2006-03-01;> > > foobucket > > footenant <=== this one > > false > > > > There's a certain problem with this, in case the client is constructing > > the URLs for

Re: Multi-tenancy in radosgw

On Wed, 2 Sep 2015 14:23:33 +0200 Radoslaw Zarzynski wrote: > What is the current status of multi-tenancy support in radosgw? > I saw branch wip-ymt-5073 which looks really nice. That branch is actually an clone of wip-5073-3, only I made it build on the current code

Re: [rgw] Multi-tenancy support in radosgw

On Sat, 12 Sep 2015 00:24:27 +0200 Radoslaw Zarzynski wrote: > Each already existing user would obtain empty bucket namespace > by default. It will be possible to create user with his own, unique > namespace. [...] > 2. We will always need ID of namespace in order to

Re: cmake

On Thu, 3 Dec 2015 19:26:52 -0500 (EST) Matt Benjamin wrote: > Could you share the branch you are trying to build? (ceph/wip-5073 would not > appear to be it.) It's the trunk with a few of my insignificant cleanups. But I found a fix: deleting the CMakeFiles/ and

Re: cmake

On Thu, 3 Dec 2015 17:30:21 -0500 "Adam C. Emerson" <aemer...@redhat.com> wrote: > On 03/12/2015, Pete Zaitcev wrote: > > I'm trying to run cmake, in order to make sure my patches do not break it > > (in particular WIP 5073 added source files). Result looks like

Re: Bucket namespaces pull req. 5872

On Mon, 26 Oct 2015 16:09:41 +0100 Radoslaw Zarzynski wrote: > > The rgw_swift_account_in_url should be possible to incorporate > > in a compatible fashion (it does not add an extra next_tok()). > > According to "rgw_swift_account_in_url": I don’t see viable method for

Re: RGW multi-tenancy APIs overview

On Mon, 9 Nov 2015 21:36:47 -0800 Yehuda Sadeh-Weinraub wrote: > In the supported domains configuration, we can specify for each domain > whether a subdomain for it would be a bucket (as it is now), or > whether it would be a tenant (which implies the possibility of >