Dear Alessandra,
Thank you for pointing me to the repository, I did not know about it.
However, I noticed it is SVN (and a single repository). For a normal
use case this should be sufficient, but for the distributed nature of
this project, I would recommend git. In addition github provides easy
ways for code reviews (pull requests).
Also, having one repository per module makes it very easy to follow
the changes (otherwise a change to a module in a big repository will
clutter the history). Another benefit of this is module testing: when
a module is correctly configured (Modulefile, metadata.json, etc).
This can even be automated using travis.org (very useful for
production grade modules!).
To summarise my suggestions:
- git/mercurial is more suitable for distributed development than SVN/CVS
- Github provides a very good web interface for discussion, code
review, distributed workflow, etc.
- one repository per module so the history is not cluttered (makes it
also easy to assign issues)
Cheers,
Luke
On 23 June 2013 20:28, Alessandra Forti <[log in to unmask]> wrote:
> Dear Luke,
>
> we decided quite some time ago to put things on the www.sysman.hep.ac.uk
> repository.
>
> http://www.sysadmin.hep.ac.uk/svn/fabric-management/puppet/
>
> Birmingham and Durham already started to post there. It's not compulsory but
> certainly less dispersive if we all use the same place.
>
> cheers
> alessandra
>
>
> On 23/06/2013 20:07, L Kreczko wrote:
>>
>> Dear all,
>>
>> Just to offer a common puppet module incubation area on github:
>> https://github.com/HEP-Puppet
>> Modules should benefit from being developed in the open (if suitable) as
>> prompt feedback is possible.
>>
>> The first of my projects which might be useful to a wider (HEP) audience
>> is
>> https://github.com/HEP-Puppet/puppet-apelpublisher
>> The module focuses on the installation and configuration of an Apel EMI-3
>> publisher for SL6. Feedback (and help) is very welcome.
>> I am currently developing in the group area as it was my private area but
>> hope to change that once more members join the group. Then I would switch to
>> forking + pull requests.
>>
>> My Bristol T2/data intensive cluster config is slowly taking shape here:
>> https://github.com/uobdic/dice_T2_puppet_config
>>
>> For data input (monitoring/ role definition) I am using Foreman, which
>> works in combination with hiera.
>>
>> Cheers,
>> Luke
>
>
>
> --
> Facts aren't facts if they come from the wrong people. (Paul Krugman)
>
--
******************************************************
Lukasz Kreczko +44 (0)117 928 8724
CMS Group
School of Physics
University of Bristol
******************************************************
|