All of lore.kernel.org
 help / color / mirror / Atom feed
From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH RFC nvme-cli 0/2] auto generate hostnqn file on installation
Date: Mon, 07 Nov 2016 12:34:46 -0800	[thread overview]
Message-ID: <1478550886.5463.14.camel@linux.intel.com> (raw)
In-Reply-To: <5a2ee2fb-8104-39cc-1af3-f0fca1caa48e@grimberg.me>

On Sun, 2016-11-06@23:36 +0200, Sagi Grimberg wrote:
> > 
> > > 
> > > Not sure if it's the best way to do this as my packeging
> > > understanding is
> > > very limited, hence the RFC. the debian part is tested (don't
> > > have
> > > access to rpm distros at the moment).
> > 
> > My idea was to add a command to generate an automatic hostnqn to
> > the nvme tool instead, what would you think about that?
> 
> I'm fine with that too.

How about an extra tweak to that tool proposal? ?Have the tool have the
option to do both NQN supported formats:

A. the first format that uses a date code in which I think that is what
patch 2 in this series was trying to do

and

B. The second format the NVMe Host driver is already does in fabrics.c?

> 
> > 
> > The install scripts could then call that.
> 
> Sounds fine.

  reply	other threads:[~2016-11-07 20:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-06 19:12 [PATCH RFC nvme-cli 0/2] auto generate hostnqn file on installation Sagi Grimberg
2016-11-06 19:13 ` [PATCH RFC nvme-cli 1/2] debain: generate hostnqn file on install and remove on uninstall Sagi Grimberg
2016-11-06 19:25   ` Christoph Hellwig
2016-11-06 21:41     ` Sagi Grimberg
2016-11-14 14:55       ` Gabriel Krisman Bertazi
2016-11-06 19:13 ` [PATCH RFC nvme-cli 2/2] nvme.spec: " Sagi Grimberg
2016-11-07  8:36   ` Johannes Thumshirn
2016-11-08 10:31     ` Sagi Grimberg
2016-11-08 10:42       ` Johannes Thumshirn
2016-11-07 20:25   ` J Freyensee
2016-11-08 10:29     ` Sagi Grimberg
2016-11-06 19:24 ` [PATCH RFC nvme-cli 0/2] auto generate hostnqn file on installation Christoph Hellwig
2016-11-06 21:36   ` Sagi Grimberg
2016-11-07 20:34     ` J Freyensee [this message]
2016-11-08 10:30       ` Sagi Grimberg
2016-11-08 17:11         ` J Freyensee

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=1478550886.5463.14.camel@linux.intel.com \
    --to=james_p_freyensee@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.