[
https://issues.apache.org/jira/browse/BIGTOP-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135819#comment-14135819
]
Evans Ye edited comment on BIGTOP-1417 at 9/16/14 5:53 PM:
-----------------------------------------------------------
Hi [~jayunit100], sorry I can't reproduce the problem.
I guess I can share you my steps so that you can point me out where I can fix
in the patch or where I need to add more documentation.
Here's what I've done to prepare a Linux environment on my windows machine.
{code}
vagrant box add box-cutter/fedora20
vagrant init box-cutter/fedora20
vagrant up
vagrant ssh
{code}
in-side the VM, I do:
{code}
sudo su - root
yum -y install docker-io git
systemctl start docker
yum install https://dl.bintray.com/mitchellh/vagrant/vagrant_1.6.5_x86_64.rpm
vagrant plugin install vagrant-hostmanager
vagrant plugin install vagrant-cachier
git clone https://github.com/apache/bigtop.git
cd bigtop
wget
https://issues.apache.org/jira/secure/attachment/12667627/BIGTOP-1417.3.patch
git am --signoff <BIGTOP-1417.3.patch
cd bigtop-deploy/vm/docker-puppet
{code}
In order to show the following process more clearly, I've record a asciinema
video.
Please take a look on the [asciinema record|https://asciinema.org/a/12223] for
first 5 minutes.
And this is just my guess:
bq. It seems like it was blocked. so i went ahead and added a nohup to the RUN
ssh -d in the Dockerfile and added another command after
If you modified this, the built image might not support ssh in sub-sequence
vagrant usage.
So if this is the case, the blocked issue should be take care first.
Finally, if the solution is not intuition enough, I'm ok to cancel it and take
some advice to deliver a new one.
Big thanks for your time, [~jayunit100].
was (Author: evans_ye):
Hi [~jayunit100], sorry I can't reproduce the problem.
I guess I can share you my steps so that you can point me out where I can fix
in the patch or where I need to add more documentation.
Here's what I've done to prepare a Linux environment on my windows machine.
{code}
vagrant box add box-cutter/fedora20
vagrant init box-cutter/fedora20
vagrant up
vagrant ssh
{code}
in-side the VM, I do:
{code}
sudo su - root
yum -y install docker-io git
systemctl start docker
yum install https://dl.bintray.com/mitchellh/vagrant/vagrant_1.6.5_x86_64.rpm
vagrant plugin install vagrant-hostmanager
vagrant plugin install vagrant-cachier
git clone https://github.com/apache/bigtop.git
cd bigtop
wget
https://issues.apache.org/jira/secure/attachment/12667627/BIGTOP-1417.3.patch
git am --signoff <BIGTOP-1417.3.patch
cd bigtop-deploy/vm/docker-puppet
{code}
In order to show the following process more clearly, I've record a asciinema
video.
Please take a look on the [asciinema record|https://asciinema.org/a/12223] for
first 5 minutes.
And this is just my guess:
bq. It seems like it was blocked. so i went ahead and added a nohup to the RUN
ssh -d in the Dockerfile and added another command after
If you modified this, the built image might not support ssh in sub-sequence
vagrant usage.
So if this is the case, the blocked issue should be take care first.
Finally, if the solution is not intuition enough, I'm ok to cancel it and take
some advice to deliver a new one.
Big thanks for your time, [~jay vyas].
> Dockerize the puppetized vagrant deployer
> -----------------------------------------
>
> Key: BIGTOP-1417
> URL: https://issues.apache.org/jira/browse/BIGTOP-1417
> Project: Bigtop
> Issue Type: New Feature
> Components: deployment
> Affects Versions: 0.7.0
> Reporter: Evans Ye
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1417.1.patch, BIGTOP-1417.2.patch,
> BIGTOP-1417.3.patch
>
>
> This is one of the bigtop's dockerize task which mainly focus on deploying
> bigtop hadoop cluster using
> [bigtop-puppet|https://github.com/apache/bigtop/tree/master/bigtop-deploy/puppet]
> on top of docker containers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
