CEPH filesystem development
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: John Spray <jspray@redhat.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	Samba Technical <samba-technical@lists.samba.org>
Subject: Re: [RFC PATCH] Samba RADOS service registration
Date: Tue, 13 Feb 2018 13:29:41 +0100	[thread overview]
Message-ID: <20180213132941.0208a8b2@suse.de> (raw)
In-Reply-To: <CALe9h7dPuDOtY06RPXJ2u5wkT=j8S6D1PkwgfByuQ8y3cuP9Fg@mail.gmail.com>

Thanks for the feedback everyone...

On Tue, 13 Feb 2018 11:07:44 +0000, John Spray wrote:

> On Tue, Feb 13, 2018 at 1:25 AM, David Disseldorp <ddiss@suse.de> wrote:
...
> > I'd like to (at the very least) pack the CephFS backed share names and
> > paths into the service registration.  
> 
> Echoing back the share configuration probably isn't a good use of this
> interface -- the idea is for service daemons to register just enough
> information about themselves to report on their existence, location
> and health.

Okay, I'll keep it simple then, and just use the Ceph global instance id
and daemon name (smbd) for now.

> In the case of nfs-ganesha, we're moving toward having the option of
> consuming its share configuration from a central place like a RADOS
> object, rather than from a local text config file -- in that model, a
> UI can go look at the configuration directly rather than having the
> daemon report it back.  This is kind of a Ceph-ized version of the way
> a lot of new projects are storing their configuration in etcd.

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.

Cheers, David

  reply	other threads:[~2018-02-13 12:29 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 [this message]
2018-02-13 12:48     ` Volker Lendecke
2018-02-13 13:43       ` Samba Ceph dbwrap backend David Disseldorp
2018-02-13 19:27 ` [PATCH v2] Samba RADOS service registration 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=20180213132941.0208a8b2@suse.de \
    --to=ddiss@suse.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jspray@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox