Re: [openstack-dev] [puppet] Clarification of 'Puppet Modules' Project Scope

2015-06-23 Thread Richard Raseley
Emilien Macchi wrote: I have a preference for #1 since IMHO it makes more sense for Midokura to have their Puppet module close to their code but I would not be against having it on Stackforge. [...] If you look at contributors [1], the history shows that this module has been written by people w

Re: [openstack-dev] [puppet] Clarification of 'Puppet Modules' Project Scope

2015-06-22 Thread Emilien Macchi
Hi Richard, On 06/22/2015 01:05 PM, Richard Raseley wrote: > I am currently hoping to build consensus (or seek clarity if I am the > only one with this question) about the appropriate scope for our 'Puppet > Modules' project. > > The question in my mind is if we: > > A) Only include those module

Re: [openstack-dev] [puppet] Clarification of 'Puppet Modules' Project Scope

2015-06-22 Thread Matt Fischer
I'm torn on this. Pedantically option A makes the most sense, but option B gives us more control over the supporting modules. I like having OpenStack CI run on vswitch and ceph rather than the typical github merge process. On Mon, Jun 22, 2015 at 11:05 AM, Richard Raseley wrote: > I am currently

[openstack-dev] [puppet] Clarification of 'Puppet Modules' Project Scope

2015-06-22 Thread Richard Raseley
I am currently hoping to build consensus (or seek clarity if I am the only one with this question) about the appropriate scope for our 'Puppet Modules' project. The question in my mind is if we: A) Only include those modules which represent a 1:1 mapping with other OpenStack projects. B) Al