From: Jeffrey Altman <jaltman@auristor.com>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: 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:23:59 -0500 [thread overview]
Message-ID: <409e0dcb-0e6e-b37a-d8d1-039f92d466ac@auristor.com> (raw)
In-Reply-To: <20170116171708.GC2953@fieldses.org>
[-- Attachment #1.1: Type: text/plain, Size: 550 bytes --]
> 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.
Jeffrey Altman
AuriStor, Inc.
[-- Attachment #1.2: jaltman.vcf --]
[-- Type: text/x-vcard, Size: 410 bytes --]
begin:vcard
fn:Jeffrey Altman
n:Altman;Jeffrey
org:AuriStor, Inc.
adr:Suite 6B;;255 West 94Th Street;New York;New York;10025-6985;United States
email;internet:jaltman@auristor.com
title:Founder and CEO
tel;work:+1-212-769-9018
note;quoted-printable:LinkedIn: https://www.linkedin.com/in/jeffreyaltman=0D=0A=
Skype: jeffrey.e.altman=0D=0A=
url:https://www.auristor.com/
version:2.1
end:vcard
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4057 bytes --]
next prev parent reply other threads:[~2017-01-16 17:32 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 [this message]
2017-01-16 17:42 ` Chuck Lever
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=409e0dcb-0e6e-b37a-d8d1-039f92d466ac@auristor.com \
--to=jaltman@auristor.com \
--cc=green@linuxhacker.ru \
--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).