The initial plan was to stop the fragmentation and centralize efforts in the stackforge module. I think we were all able to agree on that. We’ve had rather long discussions on the mailing list (https://groups.google.com/a/puppetlabs.com/forum/#!topic/puppet-openstack/ibnrmXBAxVg) and eventually drafted a blueprint:https://wiki.openstack.org/wiki/Puppet-openstack/ceph-blueprint
As far as licensing goes, Enovance’s puppet-ceph was told to become Apache2 to make it easier to pull code from their version of puppet-ceph and it’s many forks and branches (including DTAG’s). As far as I can remember, Sebastien Han told me they had agreed with their contributors to change the license to Apache2 but I have not seen that happening. I for one welcomed the stackforge initiative but have had limited resources to actually contribute new code only recently. I provide insight and reviews currently. David Moreau Simard > On Mar 10, 2014, at 12:21 PM, Florian Haas <flor...@hastexo.com> wrote: > >> 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@vger.kernel.org/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 majord...@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
