From: Chuck Lever <chuck.lever@oracle.com>
To: 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 12:42:52 -0500 [thread overview]
Message-ID: <B992125F-7D3B-460A-9A6A-ACFBEA2607A8@oracle.com> (raw)
In-Reply-To: <409e0dcb-0e6e-b37a-d8d1-039f92d466ac@auristor.com>
> 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.
> Jeffrey Altman
> AuriStor, Inc.
>
>
> <jaltman.vcf>
--
Chuck Lever
next prev parent reply other threads:[~2017-01-16 17:43 UTC|newest]
Thread overview: 19+ 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 [this message]
2017-01-16 17:46 ` James Bottomley
2017-01-16 20:39 ` Authentication Contexts for network file systems and Containers was " Jeffrey Altman
2017-01-16 21:03 ` [Lsf-pc] " James Bottomley
2017-01-17 16:29 ` Jeffrey Altman
2017-01-17 16:34 ` Trond Myklebust
2017-01-17 17:10 ` Jeffrey Altman
2017-01-16 17:32 ` [Lsf-pc] " James Bottomley
2017-01-16 18:02 ` Oleg Drokin
2017-01-16 18:21 ` James Bottomley
2017-01-16 18:39 ` Oleg Drokin
2017-01-16 20:58 ` James Bottomley
2017-01-17 7:00 ` Oleg Drokin
2017-01-17 14:26 ` James Bottomley
2017-01-17 17:41 ` Oleg Drokin
2017-01-17 14:56 ` James Bottomley
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=B992125F-7D3B-460A-9A6A-ACFBEA2607A8@oracle.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).