[
https://issues.apache.org/jira/browse/BIGTOP-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877108#comment-13877108
]
Evans Ye edited comment on BIGTOP-1171 at 1/21/14 2:26 AM:
-----------------------------------------------------------
[~mackrorysd]
Actually, just do {{vagrant up}} can get everything done with BIGTOP-1174
fixed. The reason you need to do {{vagrant provision --provision-with puppet}}
again is that the current puppet snipes do not specify the executing order
among hdfs daemons and {{init-hdfs.sh}}, so {{init-hdfs.sh}} failed to setup
those hdfs directories when it executed before namenode and datanode are up and
ready.
The consequence is as what you saw, {{hbase-master}} can not detect its home
folder on hdfs and hence abort itself.
However, the second time of puppet deploy works because namenode and datanodes
are all ready to go:)
was (Author: evans_ye):
[~mackrorysd]
Actually, just do {{vagrant up}} can get everything done with BIGTOP-1174
fixed. The reason you need to do {{vagrant provision --provision-with puppet}}
again is that the current puppet snipes do not specify the executing order
among hdfs daemons and {{init-hdfs.sh}}, so {{init-hdfs.sh}} failed to setup
those hdfs directories when it executed before namenode and datanode are up and
ready.
The consequence is as what you saw, {{hbase-master}} can not detect its home
folder on hdfs and hence abort itself.
However, the second time works beccause namenode and datanodes are all ready to
go:)
> Puppetize the Vagrant deployer
> ------------------------------
>
> Key: BIGTOP-1171
> URL: https://issues.apache.org/jira/browse/BIGTOP-1171
> Project: Bigtop
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 0.8.0
> Reporter: jay vyas
> Labels: patch
> Attachments: BIGTOP-1171.1.patch, BIGTOP-1171.2.patch
>
>
> The next iteration of the 1072 (vagrant recipe for deployment) would benefit
> alot from directly provisioning via puppet, rather than hardcoding the shell
> commands.
> HOW THE CURRENT PROVISiONER WORKS:
> The shell provisioner manually wget's the repos and installs components using
> yum.
> HOW THE PUPPET BASED PROVISIONER WILL WORK:
> In this JIRA, the aim will be to write a new provisioner that is puppet
> based, which simply manages a site.csv file for a default vagrant deployment.
> Then, the end users can update the site.csv, run "vagrant up", and have a
> puppet based distro up and running. The biggest advantage will be that the
> the vagrant deployer will continually be updated by the evolution of the
> puppet repos, rather than needing manual updates.
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
