[jira] [Comment Edited] (BIGTOP-2031) Vagrant docker script does not seem to honor :enable_local_repo

["Evans Ye (JIRA)" <ji...@apache.org>]

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

Evans Ye edited comment on BIGTOP-2031 at 9/11/15 6:32 PM:
-----------------------------------------------------------

Actually I managed to get this work w/o code change. So I think the function is good. You can refer to my [testing branch|https://github.com/evans-ye/bigtop/commit/18c3c2e8f3280d71bc1539063edd293d2597c5fe]. 
My test is to manually replace puppet recipes' default repo and vagrantconfig.yaml repo by bigtop-0.8 repo. Then enable local repo that has bigtop 1.0.0 built on disk. The result will be hadoop-2.6.0 packages being deployed.

There's a hidden thing in our deployment which is that whatever you do there's a default repo in puppet recipes, hence the local repo needs to have rpm number greater than the default 1.0.0 packages. If you're going to install packages older than 1.0.0, that's not gonna work. ;)


was (Author: evans_ye):
Actually I managed to get this work w/o code change. So I think the function is good. You can refer to my [testing branch|https://github.com/evans-ye/bigtop/commit/18c3c2e8f3280d71bc1539063edd293d2597c5fe]. 
My test is to manually replace puppet recipes' default repo and vagrantconfig.yaml repo by bigtop-0.8 repo. Then enable local repo that has bigtop 1.0.0 built on disk. The result will be hadoop-2.6.0 packages being deployed.

There's a hidden thing in our deployment which is that whatever you do there's a default repo in puppet recipes, hence the local repo needs to have rpm number greater than the default 1.0.0 packages.

> Vagrant docker script does not seem to honor :enable_local_repo
> ---------------------------------------------------------------
>
>                 Key: BIGTOP-2031
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2031
>             Project: Bigtop
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: 1.0.0
>            Reporter: Tom Zeng
>            Priority: Minor
>             Fix For: 1.1.0, 1.0.1
>
>
> It keeps hit the remote repo even with.
>     enable_local_repo: true
> in vagrantconfig.yaml
> Had to workaround it by hosting a local repo with 'ruby -run -ehttpd bigtop/output -p8000'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)