[
https://issues.apache.org/jira/browse/BIGTOP-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254218#comment-14254218
]
Konstantin Boudnik commented on BIGTOP-1576:
--------------------------------------------
I believe there are two different issues now:
- adding vagrant to toolchain, so that someone can rely on it for getting
correct version of vagrant and then being able to deploy a cluster to docker or
else using Puppet recipes
- how CI should do the deployment.
While the former can contribute to the latter, I don't think we should just use
them interchangeably. Roman's worry is about the size of the container, which
toolbox's stuff contributes to quite a bit. And in the reality, vagrant won't
add anything to how we _build_ stack. That's why I think making it an optional
toolchain dependency would make sense.
> Add Vagrant installation to bigtop_toolchain
> --------------------------------------------
>
> Key: BIGTOP-1576
> URL: https://issues.apache.org/jira/browse/BIGTOP-1576
> Project: Bigtop
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.8.0
> Reporter: Evans Ye
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1576.1.patch
>
>
> As [~cos]'s comment in BIGTOP-1564, this jira is going to "download the
> package and install it if the local vagrant version is lesser than expected".
> The patch will add a puppet recipe to automatically install Vagrant, helping
> to setup environment for running docker provisioner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
