[jira] [Commented] (BIGTOP-2253) Rewrite Bigtop Docker Provisioner to use native solutions and support multi-host cluster deployment

["Konstantin Boudnik (JIRA)" <ji...@apache.org>]

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

Konstantin Boudnik commented on BIGTOP-2253:
--------------------------------------------

Perhaps with DTK from Reactor8 guys (pinging [~kaiyzen] and [~rnp]) and Canonical's interest to use Bigtop for Juju using native solutions would be easier than ever.

> Rewrite Bigtop Docker Provisioner to use native solutions and support multi-host cluster deployment
> ---------------------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-2253
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2253
>             Project: Bigtop
>          Issue Type: New Feature
>          Components: docker, provisioner
>    Affects Versions: backlog
>            Reporter: Evans Ye
>            Assignee: Evans Ye
>
> h1. The background
> By the time we developed the Provisioner, there's no Docker compose, machine, swarm out there. But now, the feature set that Docker official provided is rich enough and surpass any other alternatives. OTOH, Vagrant introduced Docker integration very early, but seems no significant improvement in the past year. Not to mention that a [critical issue|https://github.com/mitchellh/vagrant/issues/3951#issuecomment-164059220] that disable the ssh provisioning is still not fixed yet and not likely to be fixed. Vagrant is great for VM, but not so good at Docker, hence we're going for a major rewrite and start to embrace Docker native solutions in Bigtop Docker Provisioner.  



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