On 05/20/2015 08:45 PM, Andy Grover wrote:

On 05/13/2015 03:12 PM, Chris Leech wrote:

quoted

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.