[
https://issues.apache.org/jira/browse/BIGTOP-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342746#comment-14342746
]
Evans Ye commented on BIGTOP-1712:
----------------------------------
+1 to the idea, and here's what I'm thinking:
It would be great to have dockerfiles stored at a central place of our code
base. I'm thing about moving Dockerfiles in *bigtop-deploy* to somewhere like
*bigtop-dockerfiles*, which might have build specific dockerfile stored as
well, and then push all the official images built from *bigtop-dockerfiles* up
to bigtop dockerhub. If we can do so:
* Users do not need to build local image by themselves to make docker
provisioner work. This improves the UX.
* Users can easily find and customize all the needed Dockerfile for their own
bigtop environment.
Do you think this make sense?
> Specification for Docker images.
> --------------------------------
>
> Key: BIGTOP-1712
> URL: https://issues.apache.org/jira/browse/BIGTOP-1712
> Project: Bigtop
> Issue Type: Bug
> Components: documentation
> Affects Versions: 0.9.0
> Reporter: jay vyas
> Fix For: 0.9.0
>
>
> Hi folks. we now have several bigtop related docker images.
> Lets create a wiki page for the scope and specification of the images which
> bigtop curates.
> - bigpetstore-load-generator.
> - the recently created https://github.com/tzolov/bigtop-centos images.
> - the existing bigtop centos images.
> As part of this, I'd like to add to that Specification that we curate the
> bigpetstore-load-generator image which I recently described on the mailing
> list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
