CEPH filesystem development
 help / color / mirror / Atom feed
From: Xiaopong Tran <xiaopong.tran@gmail.com>
To: Sage Weil <sage@inktank.com>
Cc: Tommi Virtanen <tv@inktank.com>,
	Danny Kukawka <danny.kukawka@bisect.de>,
	ceph-devel@vger.kernel.org, Jim Schutt <jaschut@sandia.gov>
Subject: Re: [PATCH] make mkcephfs and init-ceph osd filesystem handling more flexible
Date: Fri, 10 Aug 2012 10:01:46 +0800	[thread overview]
Message-ID: <50246B8A.5070504@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1208091845090.8611@cobra.newdream.net>

On 08/10/2012 09:53 AM, Sage Weil wrote:
> On Thu, 9 Aug 2012, Tommi Virtanen wrote:
>> On Thu, Aug 9, 2012 at 10:03 AM, Danny Kukawka <danny.kukawka@bisect.de> wrote:
>>> 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.
>>
>> I've written about this on the mailing list several times. We see a
>> lot of demand for Chef, but don't want to tie our hands -- Canonical
>> is working on Juju Charms, and I would like to see a mkcephfs
>> replacement that relies on just SSH connections from a workstation
>> node. We've made an explicit effort to improve the product as a whole,
>> and to make the Chef cookbook as thin as possible.
>>
>> For some reason, the threading is broken on the archive, but this is a
>> fragment of the most recent thread that talked about this:
>>
>> http://thread.gmane.org/gmane.comp.file-systems.ceph.devel/8263/focus=8265
>
> I think the real question is whether the planned "mkcephfs 2.0" is going
> to capture the equivalent functionality of being able to enumerate up
> front which osds will exist and which disks/journals they will use, and to
> bring them up.  Assuming it will (IMHO it needs to), can we make that
> compatible with the current way that mkcephfs is invoked (i.e., a
> ceph.conf file and a few command line args)?  Not everyone (and I daresay
> probably a minority) of users will be using Chef/Juju/Puppet/whatever,
> regardless of whether or not we feel that is the right way to do things
> and try to push them in that direction.
>
> In any case, since the new osd hotplugging stuff isn't available now and
> is probably still a sprint or two off, I think we should consider applying
> this patch.  We aren't recommending btrfs across the board, and cluster
> bringup is currently painful on ext4/xfs/etc.  And, Danny already did the
> work.  :)
>
> sage
> --

+1.

Rgds,

Xiaopong



  reply	other threads:[~2012-08-10  2:01 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
2012-08-09 17:12         ` Tommi Virtanen
2012-08-10  1:53           ` Sage Weil
2012-08-10  2:01             ` Xiaopong Tran [this message]
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=50246B8A.5070504@gmail.com \
    --to=xiaopong.tran@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=danny.kukawka@bisect.de \
    --cc=jaschut@sandia.gov \
    --cc=sage@inktank.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox