From: "François Charlier" <francois.charlier@enovance.com>
To: puppet-users@googlegroups.com, ceph-devel@vger.kernel.org,
puppet-openstack@puppetlabs.com
Subject: Re: Puppet modules for Ceph
Date: Fri, 10 Aug 2012 18:21:12 +0200 [thread overview]
Message-ID: <20120810162112.GG1882@potjevlesh.enovance.com> (raw)
In-Reply-To: <5006CB25.105@inktank.com>
On Jul 18 09:41, Mark Nelson wrote:
> On 7/18/12 8:58 AM, François Charlier wrote:
> >Hi,
> >
> >I'm currently working on writing a Puppet module for Ceph.
> >
> >As after some research I found no existing module, I'll start from
> >scratch but I would be glad to hear from people who would already have
> >started working or this or having any idea or pointers regarding this
> >subject.
> >
> >Thanks,
> >
> >[ By the way, I'm fc on #ceph ! ]
> >
>
> Hi Francois,
>
> That's great! You might want to look at the chef work that has been
> done as a base to start from. I'm not very familiar with what is in
> place, but Tommi or Dan may chime in later with more details. Some
> of the folks from Mediawiki were actually just talking about puppet
> modules yesterday on the IRC channel so they may be interested in
> collaborating too.
>
> Thanks,
> Mark
Hi,
I'd like to keep you updated on the progress I made so far :
- the module is published on github: https://github.com/fcharlier/puppet-ceph
- it's currently (only) able to install some MONs
- I hope to be able to add support for OSDs before next tuesday (because
I'm on vacation after that …)
- I listed the necessary “manual” actions needed to install a Ceph
cluster (gathered from the Ceph Chef Cookbook and the mkcephfs script)
on our wiki : https://labs.enovance.com/projects/puppet/wiki/Puppet-ceph
but it might still contain some errors.
- I've decided to stick with exported resources to transfer information
between the nodes.
Any comment or contribution would be much appreciated !
Sincerely,
--
François Charlier Software Engineer
// eNovance labs http://labs.enovance.com
// ✉ francois.charlier@enovance.com ☎ +33 1 49 70 99 81
// fc on OFTC / fc___ on FreeNode
--
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
next prev parent reply other threads:[~2012-08-10 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20120718-152758-+019.59-1@marduk.tchpc.tcd.ie>
2012-07-18 13:58 ` Puppet modules for Ceph François Charlier
2012-07-18 14:41 ` Mark Nelson
2012-08-10 16:21 ` François Charlier [this message]
2012-07-18 17:09 ` Tommi Virtanen
[not found] ` <CAKsDvb0Eq0amkEq=+9RrKcBv4RJ0PFwUGpzDpV8CzBHLQpMHtg@mail.gmail.com>
2012-07-18 22:21 ` Tommi Virtanen
[not found] ` <CAKsDvb2d63hDTq0LvmGL0z+yr09cNSr3ythWiqg6WVmzjxy8BA@mail.gmail.com>
2012-07-18 22:31 ` Tommi Virtanen
[not found] ` <5391f2cc-e01f-4cf4-b6cb-b4479bd15df0@puppetlabs.com>
2012-07-31 18:48 ` Tommi Virtanen
2012-07-31 18:51 ` Sage Weil
2012-07-31 19:09 ` Tommi Virtanen
2012-08-07 13:51 ` Jonathan D. Proulx
2012-08-09 17:04 ` Tommi Virtanen
2012-07-26 15:57 ` Jimmy Tang
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=20120810162112.GG1882@potjevlesh.enovance.com \
--to=francois.charlier@enovance.com \
--cc=ceph-devel@vger.kernel.org \
--cc=puppet-openstack@puppetlabs.com \
--cc=puppet-users@googlegroups.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.