From: Benny Halevy <bhalevy@primarydata.com>
To: linux-nfs <linux-nfs@vger.kernel.org>
Cc: Michael Maymann <michael@maymann.org>
Subject: Fwd: Re: [nfsv4] PNFS questions
Date: Fri, 14 Mar 2014 02:19:31 +0200 [thread overview]
Message-ID: <53224B13.4040203@primarydata.com> (raw)
In-Reply-To: <047d7bf0e158e2cae904f485b5fc@google.com>
Resending as the original message bounced back (html).
-------- Original Message --------
From: Benny Halevy <bhalevy@primarydata.com>
Date: Fri, 14 Mar 2014 01:56:44 +0200
Subject: Re: [nfsv4] PNFS questions
To: Michael Maymann <michael@maymann.org>, NFS list <linux-nfs@vger.kernel.org>
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>
Michael, the IETF mailing list is really not the right place to ask about
commercial solutions in general or linux solutions in particular.
Cc'ing the linux-nfs mailing list. Comments in line below.
On Thu, Mar 13, 2014 at 9:02 PM, Michael Maymann <michael@maymann.org>wrote:
> Hi list,
>
> I'm setting up a new BIO-HPC facility and are looking for a fault
> tolerant, scalable, fast and priceeffective storage solution.
>
> I have been looking at Coraid, Panasas and Lustre, but would like to
> investigate my options also of building my own PNFS solution. Clients are
> all Debian based.
>
> Can anyone recommend:
> 1. If PNFS is ready for production or if I should stick with a commercial
> vendor or build a Lustre solution ?
>
There is no pNFS server implementation in upstream linux yet.
We maintain a development out-of-kernel tree in git://
linux-nfs.org/~bhalevy/linux-pnfs.git
but it is not production ready.
> 2. PNFS Metadata server SW prefferably for Debian ?
>
ditto #1
> 3. PNFS Diskshelfs to be used ?
>
In pNFS terminology, these are Data Servers.
> 4. If AOE (ATA Over Ethernet) would make any sense together with PNFS ?
>
Maybe using the Block layout and AoE as the block storage transport
protocol.
> 5. PNFS GUI SW prefferably for Debian ?
>
ditto #1
> Thanks in advance :-) !
>
> BR.
> ~Maymann
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>
>
parent reply other threads:[~2014-03-14 0:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <047d7bf0e158e2cae904f485b5fc@google.com>]
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=53224B13.4040203@primarydata.com \
--to=bhalevy@primarydata.com \
--cc=linux-nfs@vger.kernel.org \
--cc=michael@maymann.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.