On Thu, May 21, 2015 at 11:04:46AM +0200, Hannes Reinecke wrote:
> 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.

It would be an interesting direction, essentially moving away from
having iscsid trying to be a central process to manage the state of all
iSCSI and instead headed towards just having the minimal needed
userspace support 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.

There's a few things to be improved on, but the userspace tools aren't
that far off from being able to run multiple iscsids.

For these kernel changes, I opted to go per-host instead of per-session
with network namespaces.  I was concerned about host wide changes
affecting sessions cross namespace.  Of course, that doesn't impact
iscsi_tcp or iser that have host-per-session behavior.

-Chris

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to