[
https://issues.apache.org/jira/browse/BIGTOP-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240518#comment-14240518
]
jay vyas edited comment on BIGTOP-1564 at 12/10/14 2:03 AM:
------------------------------------------------------------
Yup i guess so... I think we can easily just link to vagrant downloads page
above and grab rpm or deb autodetecting the linux distro ... feel free to make
a jira And we can look at it !
Maybe this can be part of Romans ci effort?
After all once in toolchain, now that we can install rpms from bigtop/output,
We just put that in jenckins , and voila! A bigtop build rpm script +
Docker-puppet which runs out smoke tests == New bigtop ci!
was (Author: jayunit100):
Yup i guess so... I think we can easily just link to vagrant downloads page
above and grab rpm or deb autodetecting the linux distro ...
> docker-puppet doesn't use vagrantconfg.yaml for configuration parameters
> ------------------------------------------------------------------------
>
> Key: BIGTOP-1564
> URL: https://issues.apache.org/jira/browse/BIGTOP-1564
> Project: Bigtop
> Issue Type: Bug
> Components: deployment
> Affects Versions: 0.8.0
> Reporter: Konstantin Boudnik
> Fix For: 0.9.0
>
>
> Looks like {{provision.sh}} has hardcoded content for puppet site.csv
> configuration file, instead of getting needed parameters from the YAML config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
