All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <jthumshirn@suse.de>
To: Lee Duncan <lduncan@suse.com>
Cc: lsf-pc@lists.linux-foundation.org, Hannes Reinecke <hare@suse.de>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC ATTEND] kernel booting using remote storage is a mess
Date: Tue, 10 Jan 2017 15:02:49 +0100	[thread overview]
Message-ID: <20170110140249.GC3721@linux-x5ow.site> (raw)
In-Reply-To: <ee864cdd-11c3-63d6-51b7-b23b984fdbc6@suse.com>

On Tue, Jan 03, 2017 at 03:44:48PM -0800, Lee Duncan wrote:
> The process of booting a Linux kernel with remote storage (such as iSCSI
> or FCoE) seems unnecessarily complicated if end users can even figure
> out how to do it. This is of course exacerbated by the fact that every
> company seems to CNA cards differently despite the iBFT standard.
> 
> If you add DM-Multipath on top of that, most bets are off on your
> chances of getting it to reliably work.
> 
> I'd like to discuss how we can get this to work in a general way given
> the world of systemd that we live in now.

As this applies to FCoE as well as iSCSI I'd be very interested in this
session as well.

Byte,
	Johannes

-- 
Johannes Thumshirn                                          Storage
jthumshirn@suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

      reply	other threads:[~2017-01-10 14:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 23:44 [LSF/MM TOPIC ATTEND] kernel booting using remote storage is a mess Lee Duncan
2017-01-10 14:02 ` Johannes Thumshirn [this message]

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=20170110140249.GC3721@linux-x5ow.site \
    --to=jthumshirn@suse.de \
    --cc=hare@suse.de \
    --cc=lduncan@suse.com \
    --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 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.