[
https://issues.apache.org/jira/browse/BIGTOP-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157545#comment-14157545
]
jay vyas commented on BIGTOP-1417:
----------------------------------
[~evans_ye] hi. okay.
- well, interesting, but irrelevant: i found a bug in apache infra :) it
downloads an old patch if you type an incorrect link when you donload a patch,
rather than error messaging.
*Now... looking at your new patch - it is distinct, but still seems to fail on
my fedora 20 box.*
- it still hangs in the exact same place it used to.
Next steps: We should go with one of the following options
- *force_host_vm* , to make a consistent docker environment or
- just *drop vagrant* for the time being, and write a custom python or shell
script that spins up a docker bigtop cluster for us.
Clearly, the docker on vagrant hanging issue is unresolved on some systems
(fedora 20 for me)... Sounds good to you?
> 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, BIGTOP-1417.4.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)
