From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Chuck Lever <chuck.lever@oracle.com>,
Jeffrey Altman <jaltman@auristor.com>
Cc: Oleg Drokin <green@linuxhacker.ru>,
lsf-pc@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [LSF/MM ATTEND] FS jitter testing, network caching, Lustre, cluster filesystems.
Date: Mon, 16 Jan 2017 09:46:58 -0800 [thread overview]
Message-ID: <1484588818.2540.43.camel@HansenPartnership.com> (raw)
In-Reply-To: <B992125F-7D3B-460A-9A6A-ACFBEA2607A8@oracle.com>
On Mon, 2017-01-16 at 12:42 -0500, Chuck Lever wrote:
> > On Jan 16, 2017, at 12:23 PM, Jeffrey Altman <jaltman@auristor.com>
> > wrote:
> >
> > > On Sun, Jan 15, 2017 at 06:38:43PM -0500, Oleg Drokin wrote:
> > > > A container support from filesystems is also very relevant to
> > > > us since Lustre
> > > > is used more and more in such settings.
> >
> > I too would be interested in participating in a discussion of
> > filesystem support for containers. In particular, how to manage
> > container identity for network filesystems so that network
> > filesystem modules such as kafs can be used to provide persistent
> > location-independent storage to containerized processes.
>
> I'm also interested in that discussion.
For identity, doesn't the UTS namespace do this? If not, what is
missing?
James
next prev parent reply other threads:[~2017-01-16 17:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 23:38 [LSF/MM ATTEND] FS jitter testing, network caching, Lustre, cluster filesystems Oleg Drokin
2017-01-16 17:17 ` J. Bruce Fields
2017-01-16 17:23 ` Jeffrey Altman
2017-01-16 17:42 ` Chuck Lever
2017-01-16 17:46 ` James Bottomley [this message]
[not found] ` <1484588818.2540.43.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2017-01-16 20:39 ` Authentication Contexts for network file systems and Containers was " Jeffrey Altman
2017-01-16 20:39 ` Jeffrey Altman
[not found] ` <c663a698-7116-76ac-25ee-c0ea35971a05-hRzEac23uH1Wk0Htik3J/w@public.gmane.org>
2017-01-16 21:03 ` [Lsf-pc] " James Bottomley
2017-01-16 21:03 ` James Bottomley
[not found] ` <1484600605.2540.73.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2017-01-17 16:29 ` Jeffrey Altman
2017-01-17 16:29 ` Jeffrey Altman
[not found] ` <7ba053a6-90af-ffc6-e8cd-9bfe0be41a18-hRzEac23uH1Wk0Htik3J/w@public.gmane.org>
2017-01-17 16:34 ` Trond Myklebust
2017-01-17 16:34 ` Trond Myklebust
[not found] ` <1484670853.4725.1.camel-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2017-01-17 17:10 ` Jeffrey Altman
2017-01-17 17:10 ` Jeffrey Altman
[not found] ` <D863EDBD-277B-4CC3-854F-D57FF4501542-SOTZviwpzew/JUsKyNonYw@public.gmane.org>
2017-01-16 17:32 ` [Lsf-pc] " James Bottomley
2017-01-16 17:32 ` James Bottomley
2017-01-16 18:02 ` Oleg Drokin
2017-01-16 18:21 ` James Bottomley
2017-01-16 18:39 ` Oleg Drokin
[not found] ` <9CA51BCE-7FF9-4212-9C43-B8B3667E7E6D-SOTZviwpzew/JUsKyNonYw@public.gmane.org>
2017-01-16 20:58 ` James Bottomley
2017-01-16 20:58 ` James Bottomley
[not found] ` <1484600330.2540.69.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2017-01-17 7:00 ` Oleg Drokin
2017-01-17 7:00 ` Oleg Drokin
[not found] ` <AE738992-D640-48B1-B7C3-E4E798504F7A-SOTZviwpzew/JUsKyNonYw@public.gmane.org>
2017-01-17 14:26 ` James Bottomley
2017-01-17 14:26 ` James Bottomley
[not found] ` <1484663167.2433.8.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2017-01-17 17:41 ` Oleg Drokin
2017-01-17 17:41 ` Oleg Drokin
2017-01-17 14:56 ` James Bottomley
2017-01-17 14:56 ` James Bottomley
[not found] ` <1484590862.2540.51.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2017-01-16 18:39 ` Oleg Drokin
[not found] ` <F7FABA22-8B7D-4C77-A360-4454A5571C8F-SOTZviwpzew/JUsKyNonYw@public.gmane.org>
2017-01-16 18:21 ` James Bottomley
[not found] ` <1484587952.2540.42.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2017-01-16 18:02 ` Oleg Drokin
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=1484588818.2540.43.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=chuck.lever@oracle.com \
--cc=green@linuxhacker.ru \
--cc=jaltman@auristor.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.