Are there any plans to get it upstream? if yes which kernel version?
On Wednesday, May 13, 2015 at 3:13:18 PM UTC-7, Chris Leech wrote:
I've had a few reports of people trying to run iscsid in a container,
which
doesn't work at all when using network namespaces. This is the start of
me
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
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.
On Wed, May 20, 2015 at 11:45:43AM -0700, 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
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.
I've had a few reports of people trying to run iscsid in a container, which
doesn't work at all when using network namespaces. This is the start of me
looking at what it would take to make that work, and if it makes sense at all.
The first issue is that the kernel side of the iSCSI netlink