You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/12/02 15:01:08 UTC

[jira] [Commented] (BIGTOP-2615) Provide a tool to build pseudo cluster docker images

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

ASF GitHub Bot commented on BIGTOP-2615:
----------------------------------------

GitHub user evans-ye opened a pull request:

    https://github.com/apache/bigtop/pull/165

    BIGTOP-2615. Provide a tool to build pseudo cluster docker images

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/evans-ye/bigtop BIGTOP-2615

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/bigtop/pull/165.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #165
    
----
commit 1d6c547054879e3fa34aa32d74b303782f059832
Author: Evans Ye <ev...@apache.org>
Date:   2016-12-02T15:01:50Z

    BIGTOP-2615. Provide a tool to build pseudo cluster docker images

----


> Provide a tool to build pseudo cluster docker images
> ----------------------------------------------------
>
>                 Key: BIGTOP-2615
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2615
>             Project: Bigtop
>          Issue Type: New Feature
>          Components: docker
>    Affects Versions: 1.1.0
>            Reporter: Evans Ye
>            Assignee: Evans Ye
>         Attachments: Hadoocker Design Concept.pdf
>
>
> This JIRA implements a tool named Hadoocker, which is to build docker images that have specified hadoop components provisioned inside. During image build time, we execute puppet apply to install packages and configuration. After images are built, components can be brought up quickly by executing puppet apply again. Usually it takes about 80~180 seconds, depends on the complexity of components.
> This work adopt exactly the same idea introduced by [~cos] in BIGTOP-2296, but goes further to implement a tool that supports different OS, components, or even a customized site.yaml config file.
> Use cases for Bigtop users:
> * Quick POC environment
> * Being leveraged in CI/CD pipeline
> Use cases for Bigtop:
> * Image generation CI jobs can be treated as our integration tests.



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