CEPH filesystem development
 help / color / mirror / Atom feed
From: mdw@linuxbox.com
To: Andrew Bartlett <abartlet@catalyst.net.nz>
Cc: Sage Weil <sage@newdream.net>,
	ceph-devel@vger.kernel.org, daniel.vanderster@cern.ch
Subject: Re: kerberos / AD requirements, blueprint
Date: Wed, 22 Oct 2014 18:46:06 -0400	[thread overview]
Message-ID: <20141022224605.GA1152@soma.private.linuxbox.com> (raw)
In-Reply-To: <1413951689.9184.3.camel@catalyst.net.nz>

On Wed, Oct 22, 2014 at 05:21:29PM +1300, Andrew Bartlett wrote:
...
> > At a large site, I think you can confidently expect:
> > 	or or more large scale deployments of AD,MIT,openldap,etc.
> > 	homebrew management system to provision and manage accounts
> > 	the filesystem group(s) and the identity management group are separate
> 
> Do you see a lot of this beyond major universities and similar sites?  I
> ask because at least from my Samba background, I feel like we lost out
> in the 2000's against AD, with a good number of very passionate users
> waiting patiently for Samba4, but so, so many just running AD from
> Microsoft.  The number with OpenLDAP and Kerberos that come past the
> Samba lists seemed vanishingly small. 
> 
> (I've very glad for our passionate OpenLDAP and Kerberos users, I just
> don't see so many of them these days).

I think the overwhelming common implementation is AD - at all sizes
of organizations from small to large.  But most of those will be
microsoft-only environments, so aren't particularly relevant to ceph.
I don't have good stats on the # of openldap/mit sites - but I imagine
many of them either don't care about samba, or have already invested
effort in a more or less parallel AD setup.  If you're running a lot
of microsoft desktops already, you'd have to be pretty passionate
to not just run AD and call it a day.  For ceph, though, you're
talking about linux machines - and there, the attraction for AD
is underwhelming.

					-Marcus Watts

  reply	other threads:[~2014-10-22 22:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 19:57 kerberos / AD requirements, blueprint Sage Weil
2014-10-17  0:52 ` mdw
2014-10-22  4:21   ` Andrew Bartlett
2014-10-22 22:46     ` mdw [this message]
2014-10-23  7:45       ` Christoph Hellwig
2014-10-22 16:39 ` Dan Van Der Ster
2014-10-22 17:08   ` Sage Weil
2014-10-23  8:32     ` Dan Van Der Ster
2014-10-23 14:19   ` Andrea Ieri
2014-10-23 14:47     ` Matt W. Benjamin
2014-10-23 14:51       ` Matt W. Benjamin
2014-10-23 15:05       ` Sage Weil

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=20141022224605.GA1152@soma.private.linuxbox.com \
    --to=mdw@linuxbox.com \
    --cc=abartlet@catalyst.net.nz \
    --cc=ceph-devel@vger.kernel.org \
    --cc=daniel.vanderster@cern.ch \
    --cc=sage@newdream.net \
    /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