[
https://issues.apache.org/jira/browse/BIGTOP-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865089#comment-13865089
]
Evans Ye edited comment on BIGTOP-1171 at 1/8/14 5:29 AM:
----------------------------------------------------------
Hi Jay, thanks a million for the test & feedback.
About the test procedure, sorry I didn't expain it clearly.
Originally when you do {{vagrant up}}, it will automatically do {{vagrant
provsion}} for you.
The reason why you need to do {{vagrant provision --provision-with puppet}}
again is that in our puppet snipes, init-hdfs script will be executed before
hdfs daemons are up.
When the second time you run puppet provisioner, hdfs daemons are all
set(started by first try) so that the init-hdfs script can setup hdfs folders
successfully and hbase master can be started up to work.
This will be fixed by specifying the dependency on init-hdfs script which I've
post in BIGTOP-1174.
For the hbase-test script you just mentioned on your last comment, I'm thinking
about why don't we use the same syntax as the test script you posted? So here
comes patch version 2. This will be faster and more clearly than previous one.
Here's the test output I got:
{code}
$ ./hbase-test.sh
14/01/08 03:09:39 WARN conf.Configuration: hadoop.native.lib is deprecated.
Instead, use io.native.lib.available
HBase Shell; enter 'help<RETURN>' for list of supported commands.
Type "exit<RETURN>" to leave the HBase Shell
Version 0.94.12, rUnknown, Thu Oct 31 04:44:54 EDT 2013
create 't1','cf1'
0 row(s) in 2.9400 seconds
put 't1', 'row1', 'cf1:q1', 'value1'
0 row(s) in 0.2470 seconds
scan 't1'
ROW COLUMN+CELL
row1 column=cf1:q1, timestamp=1389150584662, value=value1
1 row(s) in 0.1230 seconds
disable 't1'
0 row(s) in 1.1350 seconds
drop 't1'
0 row(s) in 1.0710 seconds
{code}
When something goes wrong, the output will show you what just the same as
you're using hbase shell.
How do you think, [~jayunit100]?
was (Author: evans_ye):
Hi Jay, thanks a million for the test & feedback.
About the test procedure, sorry I didn't expain it clearly.
Originally when you do {{vagrant up}}, it will automatically do {{vagrant
provsion}} for you.
The reason why you need to do {{ vagrant provision --provision-with puppet}}
again is that in our puppet snipes, init-hdfs script will be executed before
hdfs daemons are up.
When the second time you run puppet provisioner, hdfs daemons are all
set(started by first try) so that the init-hdfs script can setup hdfs folders
successfully and hbase master can be started up to work.
This will be fixed by specifying the dependency on init-hdfs script which I've
post in BIGTOP-1174.
For the hbase-test script you just mentioned on your last comment, I'm thinking
about why don't we use the same syntax as the test script you posted? So here
comes patch version 2. This will be faster and more clearly than previous one.
Here's the test output I got:
{code}
$ ./hbase-test.sh
14/01/08 03:09:39 WARN conf.Configuration: hadoop.native.lib is deprecated.
Instead, use io.native.lib.available
HBase Shell; enter 'help<RETURN>' for list of supported commands.
Type "exit<RETURN>" to leave the HBase Shell
Version 0.94.12, rUnknown, Thu Oct 31 04:44:54 EDT 2013
create 't1','cf1'
0 row(s) in 2.9400 seconds
put 't1', 'row1', 'cf1:q1', 'value1'
0 row(s) in 0.2470 seconds
scan 't1'
ROW COLUMN+CELL
row1 column=cf1:q1, timestamp=1389150584662, value=value1
1 row(s) in 0.1230 seconds
disable 't1'
0 row(s) in 1.1350 seconds
drop 't1'
0 row(s) in 1.0710 seconds
{code}
When something goes wrong, the output will show you what just the same as
you're using hbase shell.
How do you think, [~jayunit100]?
> 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)
