[
https://issues.apache.org/jira/browse/BIGTOP-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281217#comment-14281217
]
Evans Ye commented on BIGTOP-1603:
----------------------------------
Hi [~cos], well, we now only named it {{vagrant-puppet}} instead of
{{vagrant-puppet-vm}}.
The idea of this change is to have the flexibility to add more provider under
{{vm/}} w/o messing up the folder structure. For example, we can add aws:
{format}
vagrant-puppet-docker
vagrant-puppet-vm
vagrant-puppet-aws
{format}
So, do you think it's a good way to go?
> Rename docker-puppet and vagrant-puppet to better indicate its function and
> difference
> --------------------------------------------------------------------------------------
>
> Key: BIGTOP-1603
> URL: https://issues.apache.org/jira/browse/BIGTOP-1603
> Project: Bigtop
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 0.8.0
> Reporter: Evans Ye
> Assignee: Evans Ye
> Fix For: 0.9.0
>
>
> Since we're close to the official release which brings the docker provisioner
> up to the surface. It'd be better to have component names reflect its
> function naively. (Sorry for the bad naming at the very beginning...). This
> is also a recall of [~jayunit100]'s comment in BIGTOP-1578, and I'm with him.
> The proposed change:
> {noformat}
> docker-puppet --> vagrant-puppet-docker
> vagrant-puppet --> vagrant-puppet-vm
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
