From: Wido den Hollander <wido@42on.com>
To: "Dave (Bob)" <dave@bob-the-boat.me.uk>, ceph-devel@vger.kernel.org
Subject: Re: Mourning the demise of mkcephfs
Date: Tue, 12 Nov 2013 08:22:28 +0100 [thread overview]
Message-ID: <5281D734.3060807@42on.com> (raw)
In-Reply-To: <5281192D.4090707@bob-the-boat.me.uk>
On 11/11/2013 06:51 PM, Dave (Bob) wrote:
> The utility mkcephfs seemed to work, it was very simple to use and
> apparently effective.
>
> It has been deprecated in favour of something called ceph-deploy, which
> does not work for me.
>
> I've ignored the deprecation messages until now, but in going from 70 to
> 72 I find that mkcephfs has finally gone.
>
> I have tried ceph-deploy, and it seems to be tied in to specific
> 'distributions' in some way.
>
> It is unuseable for me at present, because it reports:
>
> [ceph_deploy][ERROR ] UnsupportedPlatform: Platform is not supported:
>
>
> I therefore need to go back to first principles, but the documentation
> seems to have dropped descriptions of driving ceph without smoke and
> mirrors.
>
> The direct approach may be more laborious, but at least it would not
> depend on anything except ceph itself.
>
I myself am not a very big fan of ceph-deploy as well. Most
installations I do are done by bootstrapping the monitors and osds manually.
I have some homebrew scripts for this, but I mainly use Puppet to make
sure all the packages and configuration is present on the nodes and
afterwards it's just a matter of adding the OSDs and formatting their
disks once.
The guide to bootstrapping a monitor:
http://eu.ceph.com/docs/master/dev/mon-bootstrap/
When the monitor cluster is running you can start generating cephx keys
for the OSDs and add them to the cluster:
http://eu.ceph.com/docs/master/rados/operations/add-or-rm-osds/
I don't know if the docs are 100% correct. I've done this so many times
that I do a lot of things without even reading the docs, so there might
be a typo in it somewhere. If so, report it so it can be fixed.
Where I think that ceph-deploy works for a lot of people I fully
understand that some people just want to manually bootstrap a Ceph
cluster from scratch.
Wido
> Maybe I need to step back a version or two, set up my cluster with
> mkcephfs, then switch back to the latest to use it.
>
> I'll search the documentation again.
> --
> 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
>
--
Wido den Hollander
42on B.V.
Phone: +31 (0)20 700 9902
Skype: contact42on
next prev parent reply other threads:[~2013-11-12 7:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 17:51 Mourning the demise of mkcephfs Dave (Bob)
2013-11-11 20:37 ` Mark Kirkwood
2013-11-12 7:22 ` Wido den Hollander [this message]
2013-11-12 7:41 ` Ketor D
2013-11-12 12:23 ` Dave (Bob)
2013-11-12 12:22 ` Dave (Bob)
2013-11-12 13:56 ` Mark Nelson
2013-11-12 14:07 ` Mark Nelson
2013-11-12 15:58 ` Alfredo Deza
2013-11-12 15:53 ` Alfredo Deza
2013-11-13 3:33 ` Mark Kirkwood
2013-11-13 3:54 ` Mark Kirkwood
2013-11-14 12:27 ` Dave (Bob)
2013-11-14 13:06 ` Dave (Bob)
2013-11-14 14:25 ` Mark Nelson
2013-11-14 21:56 ` Mark Kirkwood
2013-11-18 6:05 ` Could ceph-deploy handle unknown or custom distribution? (Was: Mourning the demise of mkcephfs) Mark Kirkwood
2013-11-18 6:15 ` Mark Kirkwood
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=5281D734.3060807@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dave@bob-the-boat.me.uk \
/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.