From: Steve Dickson <steved@redhat.com>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [nfs-utils PATCH] nfs4id: a tool to create and persist nfs4 client uniquifiers
Date: Tue, 8 Feb 2022 14:52:47 -0500 [thread overview]
Message-ID: <6cfb516d-0747-a749-b310-1368a2186307@redhat.com> (raw)
In-Reply-To: <0AB20C82-6200-46E0-A76C-62345DAF8A3A@redhat.com>
On 2/8/22 11:22 AM, Benjamin Coddington wrote:
> On 8 Feb 2022, at 11:04, Steve Dickson wrote:
>
>> Hello,
>>
>> On 2/4/22 7:56 AM, Benjamin Coddington wrote:
>>> The nfs4id program will either create a new UUID from a random source or
>>> derive it from /etc/machine-id, else it returns a UUID that has already
>>> been written to /etc/nfs4-id. This small, lightweight tool is
>>> suitable for
>>> execution by systemd-udev in rules to populate the nfs4 client
>>> uniquifier.
>>>
>>> Signed-off-by: Benjamin Coddington <bcodding@redhat.com>
>>> ---
>>> .gitignore | 1 +
>>> configure.ac | 4 +
>>> tools/Makefile.am | 1 +
>>> tools/nfs4id/Makefile.am | 8 ++
>>> tools/nfs4id/nfs4id.c | 184 +++++++++++++++++++++++++++++++++++++++
>>> tools/nfs4id/nfs4id.man | 29 ++++++
>>> 6 files changed, 227 insertions(+)
>>> create mode 100644 tools/nfs4id/Makefile.am
>>> create mode 100644 tools/nfs4id/nfs4id.c
>>> create mode 100644 tools/nfs4id/nfs4id.man
>> Just a nit... naming convention... In the past
>> we never put the protocol version in the name.
>> Do a ls tools and utils directory and you
>> see what I mean....
>>
>> Would it be a problem to change the name from
>> nfs4id to nfsid?
>
> Not at all..
Good...
> and I think there's a lot of room for naming discussions about
> the file to store the id too:
>
> Trond sent /etc/nfs4_uuid
> Neil suggests /etc/netns/NAME/nfs.conf.d/identity.conf
> Ben sent /etc/nfs4-id (to match /etc/machine-id)
Question... is it kosher to be writing /etc which is
generally on the root filesystem?
By far Neil suggestion is the most intriguing... but
on the containers I'm looking at there no /etc/netns
directory.
I had to install the iproute package to do the
"ip netns identify" which returns NULL...
also adds yet another dependency on nfs-utils.
So if "ip netns identify" does return NULL what directory
path should be used?
I'm all for making things container friendly but I'm
also a fan of keeping things simple... So
how about /etc/nfs.conf.d/identity.conf or
/etc/nfs.conf.d/nfsid.conf?
>
> Maybe the tool wants an option to specify the file?
This is probably not a bad idea... It is a common practice
steved.
>
> Ben
>
next prev parent reply other threads:[~2022-02-08 22:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 12:56 [nfs-utils PATCH] nfs4id: a tool to create and persist nfs4 client uniquifiers Benjamin Coddington
2022-02-04 15:17 ` Chuck Lever III
2022-02-04 15:49 ` Benjamin Coddington
2022-02-04 18:45 ` Chuck Lever III
2022-02-04 19:44 ` Benjamin Coddington
2022-02-05 17:35 ` Chuck Lever III
2022-02-08 3:14 ` NeilBrown
2022-02-08 11:43 ` Benjamin Coddington
2022-02-08 16:04 ` Steve Dickson
2022-02-08 16:21 ` Chuck Lever III
2022-02-08 19:29 ` Steve Dickson
2022-02-08 21:18 ` Chuck Lever III
2022-02-08 22:39 ` Steve Dickson
2022-02-10 13:28 ` Benjamin Coddington
2022-02-10 15:21 ` Chuck Lever III
2022-02-10 15:47 ` Benjamin Coddington
2022-02-10 16:25 ` Chuck Lever III
2022-02-10 16:41 ` Benjamin Coddington
2022-02-10 17:11 ` Steve Dickson
2022-02-08 16:22 ` Benjamin Coddington
2022-02-08 19:52 ` Steve Dickson [this message]
2022-02-08 20:00 ` Benjamin Coddington
2022-02-08 22:30 ` Steve Dickson
2022-02-09 13:55 ` Benjamin Coddington
2022-02-09 15:23 ` Steve Dickson
2022-02-09 21:21 ` NeilBrown
2022-02-09 21:45 ` Trond Myklebust
2022-02-09 23:58 ` NeilBrown
2022-02-10 12:25 ` Benjamin Coddington
2022-02-10 22:54 ` NeilBrown
2022-02-11 13:35 ` Benjamin Coddington
2022-02-13 23:24 ` NeilBrown
2022-02-14 11:34 ` Benjamin Coddington
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=6cfb516d-0747-a749-b310-1368a2186307@redhat.com \
--to=steved@redhat.com \
--cc=bcodding@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