From: Dan Mick <dan.mick@inktank.com>
To: Sebastien Han <sebastien.han@enovance.com>
Cc: ceph-users@lists.ceph.com, ceph-devel@vger.kernel.org
Subject: Re: [ceph-users] Puppet modules for Ceph finally landed!
Date: Thu, 28 Mar 2013 21:26:28 -0700 [thread overview]
Message-ID: <515517F4.3030501@inktank.com> (raw)
In-Reply-To: <2C8FAE48-A968-4999-A7B7-20A8D47805CE@enovance.com>
This is pretty cool, Sébastien.
On 03/28/2013 02:34 AM, Sebastien Han wrote:
> Hello everybody,
>
> Quite recently François Charlier and I worked together on the Puppet
> modules for Ceph on behalf of our employer eNovance. In fact, François
> started to work on them last summer, back then he achieved the Monitor
> manifests. So basically, we worked on the OSD manifest. Modules are in
> pretty good shape thus we thought it was important to communicate to the
> community. That's enough talk, let's dive into these modules and explain
> what do they do. See below what's available:
>
> * Testing environment is Vagrant ready.
> * Bobtail Debian latest stable version will be installed
> * The module only supports CephX, at least for now
> * Generic deployment for 3 monitors based on a template file
> examples/common.sh which respectively includes mon.sh, osd.sh, mds.sh.
> * Generic deployment for N OSDs. OSD disks need to be set from the
> examples/site.pp file (line 71). Puppet will format specified disks in
> XFS (only filesystem implemented) using these options: `-f -d
> agcount=<cpu-core-number> -l size=1024m -n size=64k` and finally mounted
> with: `rw,noatime,inode64`. Then it will mount all of them and append
> the appropriate lines in the fstab file of each storage node. Finally
> the OSDs will be added into Ceph.
>
> All the necessary materials (sources and how-to) are publicly available
> (and for free) under AGPL license on Github at
> https://github.com/enovance/puppet-ceph . Those manifests do the job
> quite nicely, although we still need to work on MDS (90% done, just need
> a validation), RGW (0% done) and a more flexible implementation
> (authentication and filesystem support). Obviously comments,
> constructive critics and feedback are more then welcome. Thus don't
> hesitate to drop an email to either François (f.charlier@enovance.com
> <mailto:f.charlier@enovance.com>) or I (sebastien@enovance.com
> <mailto:sebastien@enovance.com>) if you have further questions.
>
> Cheers!
>
> ––––
> Sébastien Han
> Cloud Engineer
>
> "Always give 100%. Unless you're giving blood."
>
>
>
>
>
>
>
>
>
> PHONE : +33 (0)1 49 70 99 72 – MOBILE : +33 (0)6 52 84 44 70
> EMAIL : sebastien.han@enovance.com
> <mailto:sebastien.han@enovance.com> – SKYPE : han.sbastien
> ADDRESS : 10, rue de la Victoire – 75009 Paris
> WEB : www.enovance.com – TWITTER : @enovance
>
>
>
> _______________________________________________
> ceph-users mailing list
> ceph-users@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>
--
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
prev parent reply other threads:[~2013-03-29 4:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 9:34 Puppet modules for Ceph finally landed! Sebastien Han
2013-03-29 4:26 ` Dan Mick [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=515517F4.3030501@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@lists.ceph.com \
--cc=sebastien.han@enovance.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.