From: sagi@grimberg.me (Sagi Grimberg)
Subject: NVMf initiator persistent across boots
Date: Wed, 30 Aug 2017 12:37:47 +0300 [thread overview]
Message-ID: <4c266ac3-a471-bb4a-c596-82270082c346@grimberg.me> (raw)
In-Reply-To: <6cdc2a01691ce8dd501987c646519a95@linux.vnet.ibm.com>
Hi,
> Could we have NVMf initiator setup persistent across boots ?
>
> Is this a possibility ? If yes, I would like suggestions on how this
> could be implemented.
We could add a systemctl one-shot add-on that would
issue nvme connect-all for each line available in
the discovery.conf file.
Something like:
--
[Unit]
Description=NVMf auto discovery service
After=systemd-modules-load.service network-online.target
[Service]
Type=oneshot
ExecStart=/usr/bin/nvme connect-all
StandardOutput=journal
[Install]
WantedBy=multi-user.target
--
Where discovery.conf would have the relevant parameters
like:
--
--traddr=<traddr1> --trsvcid=<trsvcid1>
--traddr=<traddr2> --trsvcid=<trsvcid2>
--
One thing we may want to have is to make sure
that nvme relevant modules are loaded at boot time
so we may want nvme-cli to either manually load them
or the installation would add them to systemd-modules-load.service
(i.e. add relevant files to /etc/modules-load.d/)
Thoughts?
next prev parent reply other threads:[~2017-08-30 9:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 15:00 NVMf initiator persistent across boots Narasimhan V
2017-08-30 9:37 ` Sagi Grimberg [this message]
2017-08-30 9:45 ` Johannes Thumshirn
2018-03-04 15:56 ` Max Gurtovoy
2018-03-05 19:45 ` Sagi Grimberg
2018-03-07 12:47 ` Max Gurtovoy
2018-03-08 8:39 ` Johannes Thumshirn
2018-03-08 10:03 ` Max Gurtovoy
2018-03-08 10:13 ` Johannes Thumshirn
2018-03-08 13:15 ` Max Gurtovoy
2018-03-08 13:26 ` Johannes Thumshirn
2018-03-08 17:04 ` Max Gurtovoy
2018-03-09 7:52 ` Johannes Thumshirn
2018-03-07 15:48 ` Hannes Reinecke
2018-03-07 16:36 ` Max Gurtovoy
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=4c266ac3-a471-bb4a-c596-82270082c346@grimberg.me \
--to=sagi@grimberg.me \
/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.