From: Hannes Reinecke <hare-l3A5Bk7waGM@public•gmane.org>
To: Andy Grover <agrover-H+wXaHxf7aLQT0dZR+AlfA@public•gmane.org>,
open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public•gmane.org,
linux-scsi-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public•gmane.org
Subject: Re: [RFC PATCH 0/4] Make iSCSI network namespace aware
Date: Thu, 21 May 2015 11:04:46 +0200 [thread overview]
Message-ID: <555D9FAE.5060905@suse.de> (raw)
In-Reply-To: <555CD657.6080004-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 05/20/2015 08:45 PM, Andy Grover wrote:
> On 05/13/2015 03:12 PM, Chris Leech wrote:
>> This is only about the structures and functionality involved in
>> maintaining the
>> iSCSI session, the SCSI host along with it's discovered targets
>> and devices has
>> no association with network namespaces.
>>
>> These patches are functional, but not complete. There's no
>> isolation enforced
>> in the kernel just yet, so it relies on well behaved userspace. I
>> plan on
>> fixing that, but wanted some feedback on the idea and approach so
>> far.
>
> Seems like a good direction, to me.
>
> What would be the extent of the userspace (open-iscsi) changes
> needed to go along with this?
>
What I would like to see is to split off iscsid to have one
instance/process per session.
With that we could trivially run open-iscsi in containers and
stufflike; currently it'll be hard as there really is only one
iscsid expected to be running in a system.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare-l3A5Bk7waGM@public•gmane.org +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public•gmane.org
To post to this group, send email to open-iscsi-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public•gmane.org
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2015-05-21 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 22:12 [RFC PATCH 0/4] Make iSCSI network namespace aware Chris Leech
2015-05-13 22:12 ` [RFC PATCH 3/4] iscsi: make all netlink multicast " Chris Leech
[not found] ` <1431555167-23995-1-git-send-email-cleech-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-13 22:12 ` [RFC PATCH 1/4] iscsi: create per-net iscsi nl kernel sockets Chris Leech
2015-05-13 22:12 ` [RFC PATCH 2/4] iscsi: sysfs filtering by network namespace Chris Leech
2015-05-13 22:12 ` [RFC PATCH 4/4] iscsi: set netns for iscsi_tcp hosts Chris Leech
2015-05-20 18:45 ` [RFC PATCH 0/4] Make iSCSI network namespace aware Andy Grover
[not found] ` <555CD657.6080004-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-21 9:04 ` Hannes Reinecke [this message]
2015-05-21 20:26 ` Chris Leech
2015-06-01 3:43 ` vaibhavkhanduja-Re5JQEeQqe8AvxtiuMwx3w
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=555D9FAE.5060905@suse.de \
--to=hare-l3a5bk7wagm@public$(echo .)gmane.org \
--cc=agrover-H+wXaHxf7aLQT0dZR+AlfA@public$(echo .)gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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