From: Mark Kirkwood <mark.kirkwood-6STWZtX7tXAqAMOr+u8IRA@public.gmane.org>
To: Karan Singh <karan.singh-Gn+qtVAUx6s@public.gmane.org>,
ceph-users <ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org>,
ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Ceph v0.79 Firefly RC :: erasure-code-profile command set not present
Date: Tue, 08 Apr 2014 22:12:56 +1200 [thread overview]
Message-ID: <5343CBA8.1050703@catalyst.net.nz> (raw)
In-Reply-To: <6CD10D8D-16D8-4BFE-B270-D14E11D9FCF7-Gn+qtVAUx6s@public.gmane.org>
I'm not sure if this is relevant, but my 0.78 (and currently building
0.79) are compiled from src git checkout (and packages built from the
same src tree using dpkg-buildpackage Debian/Ubuntu package builder).
Having said that - the above procedure *should* produce equivalent
binaries to the official Debian/Ubuntu and Redhat/Centos packages
(unless there is a specific bug in the rpm style builds).
Cheers
Mark
On 08/04/14 21:44, Karan Singh wrote:
> Thanks Mark for this quick checkup on Ubuntu distro. you saved my time ,
> i was also checking the same thing.
>
> All of my ceph components are on 0.79 , this looks to be a problem with
> ceph binaries for RHEL.
>
> @ Ceph Developers : Any thought on this.
>
next prev parent reply other threads:[~2014-04-08 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 8:57 Ceph v0.79 Firefly RC :: erasure-code-profile command set not present Karan Singh
[not found] ` <3423E02F-D2A2-4E7A-99BF-9B277FF3AB19-Gn+qtVAUx6s@public.gmane.org>
2014-04-08 9:28 ` Mark Kirkwood
[not found] ` <5343C143.70803-6STWZtX7tXAqAMOr+u8IRA@public.gmane.org>
2014-04-08 9:44 ` Karan Singh
[not found] ` <6CD10D8D-16D8-4BFE-B270-D14E11D9FCF7-Gn+qtVAUx6s@public.gmane.org>
2014-04-08 10:12 ` Mark Kirkwood [this message]
2014-04-08 15:01 ` [ceph-users] " Sage Weil
[not found] ` <alpine.DEB.2.00.1404080801250.28550-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-04-10 14:31 ` Karan Singh
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=5343CBA8.1050703@catalyst.net.nz \
--to=mark.kirkwood-6stwztx7txaqamor+u8ira@public.gmane.org \
--cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org \
--cc=karan.singh-Gn+qtVAUx6s@public.gmane.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.