[jira] [Comment Edited] (BIGTOP-1517) refactor vagrant provisioners to be configurable by yaml file

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

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

Evans Ye edited comment on BIGTOP-1517 at 11/6/14 4:03 AM:
-----------------------------------------------------------

I planed to have separated yaml file for each provisioner because of following reasons:
* Docker provisioner is slightly different than virtualbox one, for example, we can also configure boot2docker vm in docker's yaml, while these configurations do not need to be added in virtualbox.
* By separating yaml file, users can launch 2 type of cluster simultaneously for different purpose.


was (Author: evans_ye):
I planed to have separated yaml file for each provisioner because of following reasons:
* Docker provisioner is slightly different than virtualbox one, for example, we can also configure boot2docker vm in docker's yaml, while these configurations no need to be added in virtualbox.
* By separated yaml file, users can launch 2 cluster at the same time for different  purpose.

> refactor vagrant provisioners to be configurable by yaml file
> -------------------------------------------------------------
>
>                 Key: BIGTOP-1517
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1517
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: deployment
>    Affects Versions: 0.8.0
>            Reporter: Evans Ye
>            Priority: Minor
>
> In order to update the configurations of our Bigtop Hadoop provisioners(docker-puppet and vagrant-puppet), we need to modify its Vagrantfile directly. It would be better to have a yaml file for configuration management which consolidate all the things we typically care about when provisioning a cluster.



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