[
https://issues.apache.org/jira/browse/HADOOP-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029090#comment-13029090
]
Roman Shaposhnik commented on HADOOP-7157:
------------------------------------------
In general -- a strong +1 on the approach. H/W tends to go down, being
decommissioned and tinkered with so having a reliable way to re-deploy a
particular build/test environment is extremely important. Puppet fits the bill
perfectly.
Now, a couple of points on Puppet usage:
1. Not sure you need precise version strings for the kinds of packages that
are specified (and not all of them are specified, actually)
2. Minor nit: you can simplify an implementation by using an array syntax
for resource instantiation
3. What's your plan on applying proposed recipe? I think it would be nice to
have a cron job that would check it out from the apache repo and apply
> Create build hosts configurations to prevent degradation of patch validation
> and snapshot build environment
> -----------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-7157
> URL: https://issues.apache.org/jira/browse/HADOOP-7157
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Environment: Apache Hadoop build hosts
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Attachments: HADOOP-7157.patch
>
>
> Build hosts are being re-jumped, in need for configuration updates, etc. It
> is hard to maintain the same configuration across a 10+ hosts. A specialized
> service such as Puppet can be used to maintain build machines software and
> configurations at a desired level.
> Such configs should be checked into SCM system along with the of sources code.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
