[openstack-dev] [puppet][murano] Developing puppet module for Murano

Emilien Macchi emilien at redhat.com
Wed Jun 17 12:53:21 UTC 2015


Hi Serg,

On 06/17/2015 05:35 AM, Serg Melikyan wrote:
> 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.

Well, in fact, I'm sorry for you; you could not benefit of Puppet
OpenStack community. Let's fix that.

> 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?

The more recent patch to add a module in OpenStack is zaqar:
https://review.openstack.org/#/c/191942/

Two things we need to solve is the fact if you move your module to the
big tent:
* bring the module compliant (I'm working on a blueprint to explain what
is that, but you can already read what we said at the Summit:
https://etherpad.openstack.org/p/liberty-summit-design-puppet-compliant
* figure out Gerrit permissions. If the module is official, it has to be
maintained by Puppet OpenStack group, but that would mean you won't be
core on it, which is weird to me at this stage. We are facing the same
situation with puppet-monasca, (except the module lives in Stackforge
for day1).

> 
> References:
> [1] https://github.com/stackforge/fuel-library/tree/master/deployment/puppet/murano/
> [2] https://review.openstack.org/155688
> 

Thanks for taking care of that!
-- 
Emilien Macchi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150617/00440c56/attachment.pgp>


More information about the OpenStack-dev mailing list