All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danny Kukawka <danny.kukawka@bisect.de>
To: ceph-devel@vger.kernel.org
Cc: Tommi Virtanen <tv@inktank.com>, Jim Schutt <jaschut@sandia.gov>
Subject: Re: [PATCH] make mkcephfs and init-ceph osd filesystem handling more flexible
Date: Thu, 09 Aug 2012 19:03:18 +0200	[thread overview]
Message-ID: <5023ED56.9070102@bisect.de> (raw)
In-Reply-To: <CADvuQRG9DrG6irjuD8ZZcAz_grgS=9i6M6GDV0-gYWfAyje4uw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]

Am 09.08.2012 18:53, schrieb Tommi Virtanen:
> On Thu, Aug 9, 2012 at 9:46 AM, Jim Schutt <jaschut@sandia.gov> wrote:
>> I'm embarrassed to admit I haven't been keeping up with this,
>> but I seem to recall that early versions didn't handle a
>> journal on a partition.  Did I get that wrong, or maybe that
>> capability exists now?  In the past I've found it to have a
>> small performance benefit, and would hate to lose it.
> 
> It's still not quite ready for prime time. Journal placement was cut
> out to allow us to focus on the distributed aspects of it first; those
> are now working pretty well. Putting much effort on the alternative is
> probably not a good bet.
> 
> This ticket needs to get fixed (and defined better, first!) to have
> more flexibility with journals:
> http://tracker.newdream.net/issues/2398

So you mean chef?! Will there be an alternative to simply setup a
cluster from console?

We (SUSE) are already working on an own chef ceph cookbook. But from
what I've seen till now it's really hard and more laborious to initially
setup a cluster with chef than with mkcephfs.

Danny


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  reply	other threads:[~2012-08-09 17:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 15:42 [PATCH] make mkcephfs and init-ceph osd filesystem handling more flexible Danny Kukawka
2012-08-09 16:26 ` Tommi Virtanen
2012-08-09 16:46   ` Jim Schutt
2012-08-09 16:53     ` Tommi Virtanen
2012-08-09 17:03       ` Danny Kukawka [this message]
2012-08-09 17:12         ` Tommi Virtanen
2012-08-10  1:53           ` Sage Weil
2012-08-10  2:01             ` Xiaopong Tran
2012-08-09 16:49   ` Danny Kukawka
2012-08-09 16:54     ` Tommi Virtanen
2012-08-10 15:54 ` Sage Weil
2012-08-10 16:03   ` Danny Kukawka
2012-08-10 16:12     ` Sage Weil
2012-08-10 16:57       ` Mandell Degerness
2012-08-16 22:32       ` Sage Weil
2012-08-16 22:52         ` Tommi Virtanen
2012-08-16 22:55           ` Tommi Virtanen
2012-08-16 23:40           ` Sage Weil
2012-11-02  9:58             ` Danny Al-Gaaf
2012-11-02 11:13               ` Sage Weil
2012-11-15  0:12               ` Sage Weil
2012-11-15 10:32                 ` Danny Al-Gaaf
2012-11-15 15:05                   ` Sage Weil
2012-11-21  0:23 ` Sage Weil
2012-11-21 10:20   ` Danny Al-Gaaf

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=5023ED56.9070102@bisect.de \
    --to=danny.kukawka@bisect.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jaschut@sandia.gov \
    --cc=tv@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.