linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: Configured nqn
Date: Mon, 08 Aug 2016 10:54:38 -0700	[thread overview]
Message-ID: <1470678878.2626.6.camel@linux.intel.com> (raw)
In-Reply-To: <f94a27cf-8dcf-c881-4fe9-a45d0ce7c9c6@grimberg.me>

On Mon, 2016-08-08@11:47 +0300, Sagi Grimberg wrote:
> > 
> > Hi
> 
> Hey Gili,
> 
> > 
> > I was wondering if there's a special reason why not to support
> > preconfigured initiator nqn from a file.
> > (similar to iscsi in /etc/iscsi/initiatorname.iscsi).
> 
> It was raised on the list just last week. I think Jay
> has (of was :)) volunteered.

I was going to do it, but I was waiting for a reply on confirming what
behavior people wanted to see:


"So is the request to have nvme-cli use whatever is in
/etc/nvme/hostnqn (if it exists) over the default in the nvme-fabrics
driver???So preference of hostnqn input would be:

1. --hostnqn flag
2. /etc/nvme/hostnqn
3. default hostnqn generated by nvme-fabrics driver (ex: nqn.2014
-08.org.nvmexpress:NVMf:uuid:a2d7752c-a31b-477a-a003-31a5e1c424a9)

(note 2. may contain a hostnqn different from the default)"


Gili if you are itchin' to do it, go ahead and give it a shot, just let
me know (or I can still do it w/confirmation to above). ?The discovery
fix I added to nvme-cli:

http://lists.infradead.org/pipermail/linux-nvme/2016-July/005562.html

has been merged into the nvme-cli tool by Keith.

  reply	other threads:[~2016-08-08 17:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08  8:34 Configured nqn Gili Buzaglo
2016-08-08  8:47 ` Sagi Grimberg
2016-08-08 17:54   ` J Freyensee [this message]
2016-08-16 14:08     ` Gili Buzaglo
2016-08-17 22:04       ` J Freyensee
2016-08-18  6:37         ` Gili Buzaglo
2016-08-18  9:56           ` Sagi Grimberg
2016-08-18 15:27             ` Gili Buzaglo

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=1470678878.2626.6.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 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).