From: james_p_freyensee@linux.intel.com (Jay Freyensee)
Subject: [PATCH] nvmetcli: More refined cleanup of README
Date: Thu, 28 Jul 2016 10:37:06 -0700 [thread overview]
Message-ID: <1469727426-1178-1-git-send-email-james_p_freyensee@linux.intel.com> (raw)
Adds a few more tidbits to the README file, minus
discovery/referral info (still WIP).
Signed-off-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
---
README | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/README b/README
index 82d63ab..4c3daac 100644
--- a/README
+++ b/README
@@ -12,6 +12,11 @@ https://github.com/agrover/configshell-fb first.
nvmetcli can be run directly from the source directory or installed
using setup.py.
+If you choose to use the provided exe 'nvmetcli', you can move
+'nvmetcli' to /usr/sbin and the file 'nvmet.service' to
+/lib/systemd/system for global management of NVMe target setups
+for the machine.
+
Common Package Dependencies and Problems
-----------------------------------------
nvmetcli uses the 'python-six' and 'pyparsing' packages
@@ -53,6 +58,13 @@ The following walks through an example using interactive mode.
...> create hostnqn
#
+# remove access of a subsystem by deleting the Host NQN
+#
+
+...> cd /subsystems/testnqn/allowed_hosts/
+...> delete hostnqn
+
+#
# Alternatively this allows any host to connect to the subsystsem. Only
# use this in tightly controller environments:
#
@@ -65,7 +77,7 @@ The following walks through an example using interactive mode.
# unused one will be used.
#
-...> cd namespaces
+...> cd /subsystems/testnqn/namespaces
...> create 1
...> cd 1
...> set device path=/dev/nvme0n1
--
2.4.3
next reply other threads:[~2016-07-28 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 17:37 Jay Freyensee [this message]
2016-07-29 20:01 ` [PATCH] nvmetcli: More refined cleanup of README Sagi Grimberg
2016-08-01 11:23 ` Christoph Hellwig
2016-08-01 18:26 ` 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=1469727426-1178-1-git-send-email-james_p_freyensee@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).