From: Jimmy Tang <jtang@tchpc.tcd.ie>
To: Yehuda Sadeh <yehuda@inktank.com>
Cc: landman@scalableinformatics.com, ceph-devel@vger.kernel.org
Subject: Re: Quick CentOS/RHEL question ...
Date: Wed, 12 Sep 2012 16:42:18 +0100 [thread overview]
Message-ID: <20120912154218.GA14887@tchpc.tcd.ie> (raw)
In-Reply-To: <CAC-hyiF3jkA_VnPM8Ty9B+GnzH2xDbun9RQs+CE4yHgAp5OfnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
On Tue, Jul 31, 2012 at 06:09:59PM -0700, Yehuda Sadeh wrote:
> On Tue, Jul 31, 2012 at 3:17 PM, Joe Landman
> <landman@scalableinformatics.com> wrote:
> > Hi folks
> >
> > I was struggling and failing to get Ceph properly built/installed for
> > CentOS 6 (and 5) last week. Is this simply not a recommended platform?
> > Please advise. Thanks!
>
> As mentioned by the other responses, it is possible to get Ceph built
> for RHEL/CentOS even though it's probably not trivial. Getting proper
> packaging for these distributions is pretty high on our list. We'd
> love to hear about specific the issues that you have had.
>
Will there also be backports of the kernel modules for cephfs and rbd?
That's probably a make or break feature for anyone using RHEL based
distros as they are not likely to want to upgrade their kernels
manually and maintain them for security fixes. I guess if there are no
kernel modules for cephfs and rbd RHEL could still be used as a osd,
mon or mds.
Jimmy.
--
Jimmy Tang
Trinity Centre for High Performance Computing,
Lloyd Building, Trinity College Dublin, Dublin 2, Ireland.
http://www.tchpc.tcd.ie/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2012-09-12 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 22:17 Quick CentOS/RHEL question Joe Landman
[not found] ` <CAMm-wcKuD98z=7n=VvmEcRY6HduKKBrJ9bMyFKmN2-3VP51iLA@mail.gmail.com>
2012-08-01 0:44 ` 袁冬
2012-08-01 0:48 ` Ryan Nicholson
2012-08-01 1:09 ` Yehuda Sadeh
2012-09-12 15:42 ` Jimmy Tang [this message]
2012-09-12 15:56 ` Sage Weil
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=20120912154218.GA14887@tchpc.tcd.ie \
--to=jtang@tchpc.tcd.ie \
--cc=ceph-devel@vger.kernel.org \
--cc=landman@scalableinformatics.com \
--cc=yehuda@inktank.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.