From: David Disseldorp <ddiss@suse.de>
To: Volker Lendecke <Volker.Lendecke@SerNet.DE>
Cc: ceph-devel@vger.kernel.org,
Samba Technical <samba-technical@lists.samba.org>
Subject: Re: Samba Ceph dbwrap backend
Date: Tue, 13 Feb 2018 14:43:29 +0100 [thread overview]
Message-ID: <20180213144329.19a94a4e@suse.de> (raw)
In-Reply-To: <20180213124838.y2jmrppzpjgsdagb@sernet.de>
On Tue, 13 Feb 2018 13:48:38 +0100, Volker Lendecke wrote:
> > Interesting. The same should be possible for Samba when we eventually
> > have a Ceph key-value store backend for Samba's dbwrap, and then use
> > Registry configuration.
>
> Is there API docs around for this key-value store?
There are a few different possible approaches to take, the simplest
would probably be to use Ceph omap directly, which is documented at:
http://docs.ceph.com/docs/master/rados/api/librados/
Locking and transactions would need to be layered atop this, possibly via
a separate Samba Object Class[1] running on the Ceph OSDs.
All theoretical at this stage unfortunately, but I hope to get some time
to work on it in the future.
Cheers, David
[1] Ceph Object Classes (slide 28)
https://www.slideshare.net/sageweil1/20150311-vault15-librados
next prev parent reply other threads:[~2018-02-13 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 1:25 [RFC PATCH] Samba RADOS service registration David Disseldorp
2018-02-13 1:46 ` Jason Dillaman
2018-02-13 2:30 ` Sage Weil
2018-02-13 11:07 ` John Spray
2018-02-13 12:29 ` David Disseldorp
2018-02-13 12:48 ` Volker Lendecke
2018-02-13 13:43 ` David Disseldorp [this message]
2018-02-13 19:27 ` [PATCH v2] " David Disseldorp
2018-02-15 18:09 ` Jeff Layton
2018-02-15 18:52 ` David Disseldorp
2018-02-15 19:05 ` Jeff Layton
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=20180213144329.19a94a4e@suse.de \
--to=ddiss@suse.de \
--cc=Volker.Lendecke@SerNet.DE \
--cc=ceph-devel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
/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.