Puppet modules organization

[Michael Scherer]

Le mardi 17 juin 2014 à 11:36 +0200, David Caro a écrit :
> Hi everyone!
> 
> I'm starting a thread to discuss the puppet modules organization.
> 
> There are two proposed ways of organizing them:
> 
> 1.- Using a unique module named ovirt_infra
> 2.- Using multiple modules, named ovirt_*
> 
> Feel free to propose other alternatives, the main points for each one are:
> 
> 1.- Everything inside one module, easy to find
> 1.- Easy to add a new class, just create the file
> 1.- Easy to create hard to maintain code
> 1.- Easy to create very interdependent code
> 
> 
> 2.- Enforces modularization of the different code (one module, one task), that
> brings
> 2.- Easier to test
> 2.- Safe to reuse
> 2.- More organized (not everything in the same place)
> 2.- It's the most common way of organizing puppet manifests, so the main
> guidelines, patterns and most of the documentation expects this way of working.
> 
> 
> Please send your comments and if too many I'll open a pad with the them for easy
> review.
> 
> 
> I vote for #2, modularized organization.


Everything would still be in the same git, just to be clear ?

I would vote for #2, and in fact, I would even as far as separating the
ovirt specific stuff from the "functionnal" module. But this can be done
later.


-- 
Michael Scherer
Open Source and Standards, Sysadmin



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20140623/e5d763ed/attachment.sig>