Hi Emilien, I would like to answer your question regarding stackforge/puppet-murano repository asked in different thread:
> Someone from Fuel team created first the module in Fuel, 6 months ago > [1] and 3 months later someone from Fuel team created an empty > repository in Stackforge [2]. By the way, Puppet OpenStack community > does not have core permissions on this module and it's own by Murano team. Murano was included to Fuel around 2 years ago, our first official release as part of Fuel was Icehouse - yes, we have puppet module for Murano for a long time now. But until recently we didn't had a Big Tent in place and that is why we never thought that we able to upstream our module. Once policy regarding upstream puppet modules in Fuel changed and Big Tent model was adopted we decided to upstream module for Murano. I am really sorry that I didn't contact you for more information how to do that properly and just created corresponding repository. I didn't give permission to Puppet OpenStack community for this repository because it would be strange, given I didn't even contact you. We thought that we would upstream what we have now and then make sure that this repo will be integrated with Puppet OpenStack ecosystem. We still have big desire to upstream our puppet module. Fuel is not only user of this module, there are other projects who would like to use Murano as part of they solution and use puppet module from Fuel for deployment. Can you advise how we should proceed further? References: [1] https://github.com/stackforge/fuel-library/tree/master/deployment/puppet/murano/ [2] https://review.openstack.org/155688 -- Serg Melikyan, Senior Software Engineer at Mirantis, Inc. http://mirantis.com | smelik...@mirantis.com __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev