[
https://issues.apache.org/jira/browse/BIGTOP-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254343#comment-14254343
]
Konstantin Boudnik commented on BIGTOP-1576:
--------------------------------------------
I think it's a mea culpa: I have expressed a half-ass idea about adding this to
the toolchain without much thinking. How about a somewhat better idea: what if
we add a new manifest to the toolchain, that will not be tie-up into the
build-specific toolchain, yet will be providing us with whatever we might need
for deployment, etc.? Say, the build stuff is getting added via
{{installer.pp}} manifest. What if we add {{deployment-tools.pp}} to handle
other tools?
> 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)
