
--=-GoS11saLxRw+sj5i/l+X Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Le lundi 23 juin 2014 =C3=A0 16:42 +0200, Ewoud Kohl van Wijngaarden a =C3=A9crit :
On Mon, Jun 23, 2014 at 04:30:55PM +0200, Michael Scherer wrote:
Hi, =20 so following the discussion on puppet module, I would propose that we create a new infra-puppet-modules module on gerrit.=20 =20 The division between this module and the current one would be like this : =20 infra-puppet would hold the manifests, the site, the Puppetfile , etc =20 infra-puppet-modules would hold directories, 1 per module we develop (not the external one we use, they would still be on github or anywhere= , pulled by librarian-puppet) . =20 Since we are using librarian-puppet ( https://github.com/rodjek/librarian-puppet ) and r10k =20 We're only using r10k, not librarian-puppet.
( https://github.com/adrienthebo/r10k ) , it requires use to have the modules/ directory to be managed by librarian-puppet. In turn we need t= o have the modules in git, we can address them by path:=20 =20 mod "puppetlabs/apt", :git =3D> "git://github.com/fake/puppet-modules.git", :path =3D> "modules/apt" =20 =20 This wouldn't requires to change much, besides adding the module to Pup=
Indeed.=20 But in the end, we still use Puppetfile nonetheless, no ? petfile and creating a git repository.
=20 If no one disagree, I will request the git repository. =20 ( in the mean time, i did create a sample awstats repository for stats.= ovirt.org, so we can have something to push ) =20 Unless we plan to make them reusable for other projects, I don't see the benefit. If we do plan to make them reusable, we should IMHO also publish them on the forge. =20 Another potential issue is how we decide when to deploy. We could have a specific commit ID and update our Puppetfile every time, but again, little benefit over having them in one tree.
I was under the impression you could just give a tag and so use master ? ( and using branch for development )
In case you're unaware, we already load modules/* (which is managed by r10k) and site/* (tracked in git). That means we can host our modules in site and spit off when they are reusable.
It was not very obvious that site/* was for modules, indeed :) But my fault, I should also have read the doc in the git repository who clearly say that. I must also say that using r10k for different environments seems a bit overkill, as we seem to only have 1 single environment anyway ( but I am not using r10k usually, as I do not have enough systems for that and write all stuff myself ).=20
And if we do plan on creating modules repos, I'd be in favor of having one git repo per puppet module since that is what most people would expect.
One git repo per module is a bit annoying when we are planning to write a lot of modules. But I guess it all depend on the time it take to create one. I would definitely prefer a approach of 1 big git as long as we are "growing" fast and maybe split later, since it permit faster growth ? --=20 Michael Scherer Open Source and Standards, Sysadmin --=-GoS11saLxRw+sj5i/l+X Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAABAgAGBQJTqE+rAAoJEE89Wa+PrSK9eSQP/2IJxedKswUoVphKXKsp+Lox FfabCRRosySEQ31tD2F8VZvzB0Xy/SPrdyK/4H9u+G4H1t6FazZfPkh4q2abo4F6 JgZSZP++bNiIozrlXRNqYRJa0jcQli3oPnpjWzXDunhXI+8SXkejeN7jtUmydOxj Y6dzjaEHLSsggke9Uk42PmRPdXVLLdNyP7e8fRdMIHfP8+OvJm9X52Cz86JPPv2f hUBLkam5ZNwWgQEaPSSvPy+LGo4FBnvJ9yeGa5ODNiU2NvFtve0wsx9hRdVkOZzx lO7rx22a6AYcfYrpJhroFZA8bzkegGiDp6kzVkogvkFtlfDazKZycXsu2idJqYQR uKXjjf+H+ERhfpZ6FfEXDoypgaqlRK4eceinSgBfMv/wqGtSx9TZe7NqvHBTmgLA R/0aw/3SlGdVsWKFgaxaZW6ZIeh/PvCc83XJtuy8EjkEBIQeCR18Sz2zggjes/FB jpZHCJwUOdbCGh9L1Lpo6phuJNTuVOC5r9xjk2NIfFMWtFyDCakecH1ncdtvvK/B 3czgGauq3Opz04cAx1f1nPAj8Q1Mrv53N6MvQfT+3IJ8vjdXsINyPrJ4aJvSCYBM T6mr9vAYHPZHsPHwSj9FLwm27lIRdfDnPlOe1Y1KvPEZbEj++h3y7n8aoShmEoe4 waKCRscrjNh1oMb4ff+l =zOY/ -----END PGP SIGNATURE----- --=-GoS11saLxRw+sj5i/l+X--