[LSF/MM/BPF TOPIC] network storage transports managed within a container

Hannes Reinecke hare at suse.de
Mon Mar 14 05:50:31 PDT 2022


On 3/1/22 20:20, Lee Duncan wrote:
> On 2/28/22 18:04, Chris Leech wrote:
>> There are various challenges when users start trying to manage SAN
>> attachments from within a container, and how we deal with network
>> namespaces.  I think it would be worth a discussion around what can be
>> agreed on as desired behavior, and what it means to attach block
>> devices from a containerized environment.
>>
>> iSCSI has a number of issues here with the kernel to iscsid
>> interfaces, netlink and sysfs, which are largely fixable without
>> needing to break anything.  But for kernel maintained network
>> connections, there's an issue of interacting with namespace lifetimes
>> without a process.
>>
>> NVMe/TCP has avoided complex user-space control planes, but when I
>> checked subsystem connection occurred within the active namespace of
>> nvme-cli, but afterwords all fabrics subsystems were visible,
>> controllable, and disconnectable from any namespace.
>>
>>
>> Lee Duncan had submitted a proposal to discuss this for iSCSI last
>> year [1], partially based on some older work I did that never
>> completed [2] (I need to update that code)
>>
>> [1]
>> https://lore.kernel.org/linux-scsi/e9f0297a-a914-ba83-f706-5a2d508c666b@suse.com/ 
>>
>>
>> [2] https://github.com/cleech/linux/commits/iscsi-netns-old-wip
>>
>> - Chris Leech
>>
> 
> I would certainly be interested in attending this.
> 
Count me in.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		           Kernel Storage Architect
hare at suse.de			                  +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer



More information about the Linux-nvme mailing list