linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <steved@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: [RFC PATCH 0/1] Create a DNS SRV record of the ID mapping domain
Date: Mon, 23 May 2016 12:18:26 -0400	[thread overview]
Message-ID: <1464020307-8806-1-git-send-email-steved@redhat.com> (raw)

I have a customer that requested the domain used
to do the ID mapping be available via DNS SVR 
record. I didn't think was that bad of an idea. 

IPA and FedFS use SRV records which seem to work out
pretty well. This patch is heavily based on the 
FedFS code. ;-) 

My only question is do we want libnfsidmap to be
dependent on the resolver library. There has been
some talk about moving libnfsidmap into nfs-utils
which means nfs-utils would be dependent the
resolver library. 

Note, this is not complete. If we are going to do
this I have to document it somehow, either in 
the man page or idmap.conf or both.

Just looking for thoughts... good/bad idea??

Steve Dickson (1):
  libnfsidmap: Query DNS for the NFSv4 ID domain

 configure.ac  |  1 +
 libnfsidmap.c | 89 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 89 insertions(+), 1 deletion(-)

-- 
2.5.0


             reply	other threads:[~2016-05-23 16:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23 16:18 Steve Dickson [this message]
2016-05-23 16:18 ` [RFC PATCH 1/1] libnfsidmap: Query DNS for the NFSv4 ID domain Steve Dickson
2016-05-23 17:22 ` [RFC PATCH 0/1] Create a DNS SRV record of the ID mapping domain Chuck Lever
2016-05-24 16:02   ` Steve Dickson
2016-05-24 16:20     ` Chuck Lever
2016-05-24 17:43       ` Steve Dickson
2016-05-24 18:20         ` Chuck Lever
2016-05-24 19:34           ` Thomas Haynes
2016-05-24 20:57             ` Mkrtchyan, Tigran
2016-05-25 12:14           ` Steve Dickson
2016-05-25 15:25             ` Chuck Lever
2016-05-25 16:07               ` Steve Dickson
2016-05-25 16:12                 ` Chuck Lever

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=1464020307-8806-1-git-send-email-steved@redhat.com \
    --to=steved@redhat.com \
    --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).