You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "YoungWoo Kim (JIRA)" <ji...@apache.org> on 2017/02/04 04:59:52 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=15852593#comment-15852593 ] 

YoungWoo Kim commented on BIGTOP-2615:
--------------------------------------

[~evans_ye] Just curious... Is it possible to use local repo? I'd like to pull the packages from $BIGTOP_HOME/output/

> 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
>             Fix For: 1.2.0
>
>         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.15#6346)