[ 
https://issues.apache.org/jira/browse/BIGTOP-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128513#comment-13128513
 ] 

Roman Shaposhnik commented on BIGTOP-95:
----------------------------------------

Yup, all the nuts-n-bolts for making both secure and unsecure Hadoop 
deployments have been pushed. The only thing that's left is to tweak the code a 
little bit to be be 100% compatible with how Bigtop does packaging. I plan to 
work on it next week, but any help would be appreciated. Its pretty easy to 
deploy locally (without the need to run the puppet master, etc) and test the 
code: just do puppet puppet  --modulepath `pwd`/modules manifests/example.pp 
where example.pp is a  subset of a cluster.pp manifest appropriate for a single 
node testing.
                
> Puppet-based deployment infrastructure needs to be added to bigtop
> ------------------------------------------------------------------
>
>                 Key: BIGTOP-95
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-95
>             Project: Bigtop
>          Issue Type: New Feature
>          Components: General, Tests
>    Affects Versions: 0.1.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.2.0
>
>
> In order to facilitate dynamic bringup/teardown of Bigtop cluster for the 
> purposes of stack validation we need to have an infrastructure that lets us:
>    1. continuously deploy Bigtop packages from Jenkis artifacts
>    2. do the required amount of configuration management
>    3. be able to auto-deploy Bigtop dependencies such as databases, etc.
> Puppet seems to be the preferred CM solution that fits the above uses cases 
> rather well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to