From: Kasper Dieter <dieter.kasper@ts.fujitsu.com>
To: "Chen, Xiaoxi" <xiaoxi.chen@intel.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"ceph-users@ceph.com" <ceph-users@ceph.com>
Subject: Re: Any concern about Ceph on CentOS
Date: Wed, 17 Jul 2013 08:16:55 +0200 [thread overview]
Message-ID: <20130717061655.GB13122@oder.mch.fsc.net> (raw)
In-Reply-To: <6F3FA899187F0043BA1827A69DA2F7CC01E43F83@SHSMSX102.ccr.corp.intel.com>
Hi Xiaoxi,
we are really running Ceph on CentOS-6.4
(6 server nodes, 3 client nodes, 160 OSDs).
We put a 3.8.13 Kernel on top and installed the ceph-0.61.4 cluster with mkcephfs,
because ceph-deploy seems to be still very buggy and has big dependencies to the newest python.
ceph.ko
rbd.ko
and ceph-fuse are running fast, well and stable (so far ;-) ).
Cheers,
-Dieter
On Wed, Jul 17, 2013 at 03:18:22AM +0200, Chen, Xiaoxi wrote:
> Hi list,
> I would like to ask if anyone really run Ceph on CentOS/RHEL?
> Since the kernel version for Cent/RHEL is much older than that of Ubuntu,
> I am thinking about whether we have some known performance/functionality issue?
> Thanks for everyone could share your insight for Ceph+CentOS.
> Xiaoxi
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-07-17 6:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 1:18 Any concern about Ceph on CentOS Chen, Xiaoxi
[not found] ` <6F3FA899187F0043BA1827A69DA2F7CC01E43F83-0J0gbvR4kTiiAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-07-17 3:16 ` Haomai Wang
2013-07-17 6:16 ` Kasper Dieter [this message]
2013-07-17 6:22 ` Haomai Wang
[not found] ` <20130717061655.GB13122-tbq9f/Eh0BZ9QGbx8OrcVQ@public.gmane.org>
2013-07-17 6:27 ` Chen, Xiaoxi
-- strict thread matches above, loose matches on Subject: below --
2013-07-17 6:59 Kasper Dieter
2013-07-17 7:25 ` Liu Yuan
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=20130717061655.GB13122@oder.mch.fsc.net \
--to=dieter.kasper@ts.fujitsu.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@ceph.com \
--cc=xiaoxi.chen@intel.com \
/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.