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

["Olaf Flebbe (JIRA)" <ji...@apache.org>]

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

Olaf Flebbe edited comment on BIGTOP-2253 at 7/10/16 9:26 AM:
--------------------------------------------------------------

Thanks [~evans_ye]] . I had the same idea, too. Great.

On the positive side: The new Docker for Mac works like a charm. The Bind mount (-v)  is slow but sufficient to copy sources into a container and artefacts back. A great plus: The mount handles user mapping transparently. I haven't used the docker-toolbox before.

On the negative side: I still found no way to set the dnsdomainname with the new docker swarm. It worked out of the box with compose like you used it before.

Can you point me to infos on service discovery with the new swarm ? I didn't work for me like I expected it.


was (Author: oflebbe):
Thanks [~Evans Ye] . I had the same idea, too. Great.

On the positive side: The new Docker for Mac works like a charm. The Bind mount (-v)  is slow but sufficient to copy sources into a container and artefacts back. A great plus: The mount handles user mapping transparently. I haven't used the docker-toolbox before.

On the negative side: I still found no way to set the dnsdomainname with the new docker swarm. It worked out of the box with compose like you used it before.

Can you point me to infos on service discovery with the new swarm ? I didn't work for me like I expected it.

> 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)