Hi, Somehow I'm thinking I'm opening a can of worms, but here it goes anyway. I saw some discussion about this here on this list last (Northern Hemisphere) autumn, but not much since. I'd like to ask for some clarification on the current state of the Ceph Puppet modules. Currently there are several: one on StackForge (http://git.openstack.org/cgit/stackforge/puppet-ceph/), primarily written by Loïc Dachary, and one on the eNovance GitHub repo (https://github.com/enovance/puppet-ceph), written by Sébastien Han and François Charlier. The eNovance repo is AGPL licensed, which I find rather incomprehensible — the only thing this would make sense for would be to force providers of *public* Puppet hosts to contribute back upstream, but that's a really far fetched use case. The StackForge repo is ASL licensed, which looks a bit saner. Then there is a TelekomCloud fork of the eNovance repo at https://github.com/TelekomCloud/puppet-ceph/tree/rc/eisbrecher, with 55 unmerged patches. Also AGPL, as far as I can tell. And finally there's puppet-cephdeploy (https://github.com/dontalton/puppet-cephdeploy) where I like that it builds upon ceph-deploy, but rather dislike that it's rather closely interwoven with OpenStack. ASL. Finally, after the discussion that Loïc kicked off in https://www.mail-archive.com/ceph-devel@xxxxxxxxxxxxxxx/msg16673.html, there's https://github.com/ceph/puppet-ceph which hasn't seen any updates in 2 months. This is a mirror of the StackForge module, as far as I can tell, is ASL licensed and has seen neither the eNovance work nor the TelekomCloud updates, presumably on account of the license issue. Neither repo seems to be universally accepted and fully complete (StackForge only supports mon deployment; eNovance doesn't do radosgw, for example), so I'm trying to understand where people should best direct their efforts to get things to a working state. All thoughts and comments appreciated. Thanks! Cheers, Florian -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
