You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2015/01/31 21:10:35 UTC
[jira] [Comment Edited] (BIGTOP-1643) vagrant-puppet-docker to
support debian as well
[ https://issues.apache.org/jira/browse/BIGTOP-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299964#comment-14299964 ]
jay vyas edited comment on BIGTOP-1643 at 1/31/15 8:10 PM:
-----------------------------------------------------------
thanks olaf. this looks good to me.
I tested it and it appears not to break any of the core stuff (didnt test debain though).
Can you please modify the *xxx/debian* at the very end (add a comment for it)
with that modification, i give my "preapproved" +1 to go ahead and commit this patch (make sure to put the right commit message also).
overall looks like alot of hard work . [~evans_ye] please take note of this update ...
was (Author: jayunit100):
thanks olaf. this looks good to me.
I tested it and it appears not to break any of the core stuff (didnt test debain though).
Can you please modify the *xxx/debian* at the very end ?
with that modification, i give my "preapproved" +1 to go ahead and commit this patch (make sure to put the right commit message also).
overall looks like alot of hard work . [~evans_ye] please take note of this update ...
> vagrant-puppet-docker to support debian as well
> -----------------------------------------------
>
> Key: BIGTOP-1643
> URL: https://issues.apache.org/jira/browse/BIGTOP-1643
> Project: Bigtop
> Issue Type: Bug
> Reporter: Olaf Flebbe
> Assignee: Olaf Flebbe
> Attachments: 0001-BIGTOP-1643.-vagrant-puppet-docker-to-support-debian.patch
>
>
> Add support for debian in docker-hadoop.sh :
> Now option -d debian
> (default is -d centos, may not be given)
> to be used like
> ./docker-hadoop.sh -d debian -b
> ./docker-hadoop.sh -d debian -c 3
> There is a puppet problem when creating the hadoop cluster (include stdlib seems not to work correctly). Will fix it
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)