From: Loic Dachary <loic@dachary.org>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: creation of the puppet-ceph repository
Date: Sat, 25 Jan 2014 17:45:20 +0100 [thread overview]
Message-ID: <52E3EA20.4010403@dachary.org> (raw)
In-Reply-To: <CAJH6TXiHaqn7M7UF2EV_Py+D_pbQrOQQ78KrSLENGWuev6jx2Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
Hi,
At the moment I would recommend using ceph-deploy instead of puppet. Although there are puppet modules that could be used, they require significantly more work than using ceph-deploy, even for someone who already has a running puppet master. The new puppet ceph module is expected to be simpler to use than ceph-deploy and address more use cases, but it is not ready yet.
Cheers
On 24/01/2014 18:38, Gandalf Corvotempesta wrote:
> 2014/1/24 Loic Dachary <loic@dachary.org>:
>> Hi,
>>
>> At the moment the module can only be used to deploy mons. It's making slow progress but a number of patches went in Ceph and should significantly simplify writing the puppet module, starting in Firefly.
>
>
> Based on docs, OSD seems to be deployable from puppet.
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2014-01-25 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 17:39 creation of the puppet-ceph repository Loic Dachary
2013-12-16 3:46 ` Ian Colle
2013-12-16 11:43 ` Loic Dachary
2013-12-16 19:39 ` Loic Dachary
2013-12-16 19:47 ` Loic Dachary
2013-12-16 22:55 ` Ian Colle
2013-12-16 23:16 ` Loic Dachary
2013-12-16 23:24 ` Ian Colle
2013-12-16 23:32 ` Loic Dachary
2014-01-24 13:57 ` Gandalf Corvotempesta
2014-01-24 17:11 ` Loic Dachary
2014-01-24 17:38 ` Gandalf Corvotempesta
2014-01-25 16:45 ` Loic Dachary [this message]
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=52E3EA20.4010403@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=gandalf.corvotempesta@gmail.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.