You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Evans Ye (JIRA)" <ji...@apache.org> on 2016/04/24 17:56:12 UTC
[jira] [Commented] (BIGTOP-2387) New Docker provisioner destroy
will delete all docker containers on the host
[ https://issues.apache.org/jira/browse/BIGTOP-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255637#comment-15255637 ]
Evans Ye commented on BIGTOP-2387:
----------------------------------
Some description for the patch:
* leverage docker-compose -p option to specify a project name. With that we can isolate each provisioned cluster instead of using the default, global docker-compose project namespace.
* The project name is auto-generated when using --create to provision a cluster
{code}
echo "`date +'%Y%m%d_%H%M%S'`_R$RANDOM" > .provision_id
{code}
* A -l, --list option has been added into docker-hadoop.sh so that we can check container status
> New Docker provisioner destroy will delete all docker containers on the host
> ----------------------------------------------------------------------------
>
> Key: BIGTOP-2387
> URL: https://issues.apache.org/jira/browse/BIGTOP-2387
> Project: Bigtop
> Issue Type: Sub-task
> Components: docker, provisioner
> Affects Versions: backlog
> Reporter: Evans Ye
> Assignee: Evans Ye
> Attachments: BIGTOP-2387.patch
>
>
> Use docker-compose service group may solve the problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)