From: Hannes Reinecke <hare@suse.de>
To: Omar Sandoval <osandov@osandov.com>
Cc: Omar Sandoval <osandov@fb.com>,
Christian Brauner <christian.brauner@microsoft.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>
Subject: Re: [LSF TOPIC] block namespaces
Date: Mon, 2 May 2022 09:17:04 -0700 [thread overview]
Message-ID: <44814263-1546-a450-e799-5039aa991ca6@suse.de> (raw)
In-Reply-To: <YnACIcvUBH8/eKdC@relinquished.localdomain>
On 5/2/22 09:09, Omar Sandoval wrote:
> On Mon, May 02, 2022 at 01:14:48AM +0200, Hannes Reinecke wrote:
>> Hi Omar,
>>
>> here's a late topic for the I/O Track: Block namespaces
>>
>> We already proposed it for the (canceled) LSF last year, and now I found
>> that Christian Brauner is actually present here at LSF.
>>
>> What this is about: Similarly to network namespaces we'd like to explore the
>> possibility of block namespaces.
>> Canonical use-case here is iscsi sessions within containers: if one
>> container starts up an iscsi session, why should this session be visible to
>> the other containers?
>> The discussion should be about general design and possible use-cases.
>
> Hey, Hannes,
>
> How much does this overlap with Chris Leech's "network storage
> transports managed within a container" topic?
Hmm. Good question; I don't really know. But yeah, I guess there is some.
So we could lump both of them together I think.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
next prev parent reply other threads:[~2022-05-02 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 23:14 [LSF TOPIC] block namespaces Hannes Reinecke
2022-05-02 16:09 ` Omar Sandoval
2022-05-02 16:17 ` Hannes Reinecke [this message]
2022-05-02 16:21 ` Omar Sandoval
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=44814263-1546-a450-e799-5039aa991ca6@suse.de \
--to=hare@suse.de \
--cc=christian.brauner@microsoft.com \
--cc=linux-block@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=osandov@fb.com \
--cc=osandov@osandov.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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