From: Spelic <spelic@shiftmail.org>
To: linux-nfs@vger.kernel.org
Subject: Re: NFSv4 behaviour on unknown users
Date: Mon, 29 Nov 2010 23:47:20 +0100 [thread overview]
Message-ID: <4CF42D78.3010604@shiftmail.org> (raw)
In-Reply-To: <20101129195010.GA6423@hostway.ca>
On 11/29/2010 08:50 PM, Simon Kirby wrote:
> ...
> I tried to write the NFSv4 spec people, but didn't get any reply. I can
> see maybe why they would want to do this by default, but it's not like
> people don't already have years of experience with how NFSv3 and earlier
> worked, and I still think should at least be a way to request that
> behaviour.
>
Yeah!!!
currently it sucks... er...
I don't understand... never before I came across a "new version" of a
software or a protocol which allows to do many fewer things than the
older version. This sucks. Lots of use cases for NFS here are totally lost.
I'm thinking that even if I'd setup LDAP for everything here, things
would not be easy, because we have server1 which has certain users and
groups, server2+server3 which are for a different project and have
different users and groups etc... and now we need to have the NFS server
understand all those sets of users simultaneously, but the various
servers only need to understand theirs and the other people should not
be able to log in!
Maybe it's possible (I don't know how), but looks like a major headache.
And now we probably cannot even have more than one LDAP server any
longer: all LDAP probably needs to be centralized on a single machine
which is where the NFS server(s) authenticate... it looks like a real
problem for the independence of projects... and I really fear to think
of what will happen if that machine fails!
I'd be glad to go back to NFS version 3 but we need nfs on infiniband
rdma now, and afaik it's only available in version 4.
If it's still possible to change the specs or break them, well... you
sure have my vote!
Thank you
S.
next prev parent reply other threads:[~2010-11-29 22:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 17:32 NFSv4 behaviour on unknown users Spelic
2010-11-29 19:50 ` Simon Kirby
2010-11-29 22:47 ` Spelic [this message]
2010-11-30 15:20 ` Chuck Lever
-- strict thread matches above, loose matches on Subject: below --
2010-11-29 18:12 Spelic
2010-11-29 18:22 ` Trond Myklebust
2010-11-29 18:38 ` Spelic
2010-11-29 19:01 ` J. Bruce Fields
2010-11-29 19:09 ` Trond Myklebust
2010-11-30 15:36 ` Steve Dickson
2010-11-30 22:19 ` Trond Myklebust
2010-11-30 22:26 ` J. Bruce Fields
2010-11-30 22:33 ` Trond Myklebust
2010-11-30 22:36 ` J. Bruce Fields
2010-11-30 22:47 ` Trond Myklebust
2010-12-01 2:57 ` Neil Brown
2010-12-01 3:10 ` Trond Myklebust
2010-12-01 3:23 ` Neil Brown
2010-12-01 16:29 ` J. Bruce Fields
2010-12-02 23:10 ` Thomas Haynes
2010-12-02 23:18 ` Trond Myklebust
2010-12-02 23:28 ` Spencer Shepler
2010-12-08 0:15 ` 'J. Bruce Fields'
2010-12-10 19:00 ` Thomas Haynes
2010-12-10 19:17 ` J. Bruce Fields
2010-11-29 22:09 ` Daniel.Muntz
2010-11-29 22:57 ` Spencer Shepler
2010-11-29 23:16 ` Trond Myklebust
2010-11-29 23:25 ` Spencer Shepler
2010-11-29 23:26 ` Trond Myklebust
2010-11-29 23:30 ` Spencer Shepler
2010-11-29 23:40 ` Trond Myklebust
2010-11-30 0:02 ` Spencer Shepler
2010-11-30 11:44 ` Spelic
2010-11-30 13:04 ` Trond Myklebust
2010-11-30 15:48 ` Boaz Harrosh
2010-11-29 23:34 ` Daniel.Muntz
2010-11-29 23:36 ` Spencer Shepler
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=4CF42D78.3010604@shiftmail.org \
--to=spelic@shiftmail.org \
--cc=linux-nfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).