From: Lee Duncan <lduncan@suse.com>
To: lsf-pc@lists.linux-foundation.org, Hannes Reinecke <hare@suse.de>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: [LSF/MM/BPF TOPIC] discovering network iSCSI storage devices: zeroconf?
Date: Thu, 10 Jun 2021 10:16:55 -0700 [thread overview]
Message-ID: <de7c2464-687c-f1d2-bf07-9d3c20571b0f@suse.com> (raw)
The current technology for discovering network iSCSI devices is not
good. Most administrators just have to "know" the name and location of
remote storage, but this becomes problematic when there are a log of
devices (or the administrator has a bad memory).
The current "solution" for this is supposed to be open-isns, but it's
overly complicated and so generally not used.
Hannes suggesting using zeroconf (bonjour) to make storage devices
easily discoverable, but questions remain. Is this feasable? Should
open-isns be modified to also broadcast via zeroconf, or is a new daemon
needed? Does anyone else care? (Honestly, I can't judge actual demand
for this very well.)
Thanks.
--
Lee Duncan
reply other threads:[~2021-06-10 17:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=de7c2464-687c-f1d2-bf07-9d3c20571b0f@suse.com \
--to=lduncan@suse.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).