All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jevon Qiao <scaleqiao@gmail.com>
To: sage@newdream.net
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	ceph-users@ceph.com
Subject: Seek advice for using Ceph to provice NAS service
Date: Wed, 23 Sep 2015 10:21:54 +0800	[thread overview]
Message-ID: <56020CC2.2060806@gmail.com> (raw)

Hi Sage and other Ceph experts,

This is a greeting from Jevon, I'm from China and working in a company 
which are using Ceph as the backend storage. At present, I'm evaluating 
the following two options of using Ceph cluster to provide NAS service 
and I need your advice from the perspective of stability and feasibility.

Option 1: Directly use CephFS
Since Ceph as a unified storage can provide file system storage service 
via cephfs, this looks an ideal solution for my case if CephFS is ready 
to be used in production environment. However, based on the previous 
discussions on CephFS, I see that there are still some issues like not 
ready for supporting multiple metadata servers, lack of a fully 
functioning fsck and so on. Also, I learn that CephFS has been evaluated 
by a large community of users and there are production systems using it 
with a single MDS from the official website of Ceph. So it is difficult 
for me to make the decision on whether I should use it.

Option 2: Ceph rbd + NFS server
This might be a common architecture used in current NAS storage. But the 
problem is how to get rid of the single point failure on NFS server. 
What I have right now is to use Corosync and Pacemaker(the typical HA 
solution in Linux) to form a cluster. It seems that Sebastien Han has 
verified the feasibility.

Your comments/advices would be highly appreciated and I'm looking 
forward to your reply.

Thanks,
Jevon

             reply	other threads:[~2015-09-23  2:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23  2:21 Jevon Qiao [this message]
2015-09-24 14:21 ` Seek advice for using Ceph to provice NAS service Jevon Qiao

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=56020CC2.2060806@gmail.com \
    --to=scaleqiao@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-users@ceph.com \
    --cc=sage@newdream.net \
    /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.