[
https://issues.apache.org/jira/browse/METRON-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853442#comment-15853442
]
ASF GitHub Bot commented on METRON-646:
---------------------------------------
Github user kylerichardson commented on the issue:
https://github.com/apache/incubator-metron/pull/441
Good point, @nickwallen. My hope for metron-docker is as a lightweight
alternative to vagrant for development. That said, I would hate to see it
become a large overhead for the community.
Thanks for starting a dev list discussion. I'll post my thoughts there.
-Kyle
> On Feb 5, 2017, at 4:09 PM, Nick Allen <[email protected]> wrote:
>
> Hi @kylerichardson - I don't want to throw cold water on your effort, but
I am hesitant to create a third deployment code base for metron-docker (in
addition to MPack and Ansible.) Do you think that is what this is or would
become?
>
> Besides just the index templates, we'd have to add and support a lot of
other functionality too. Seems like we should have a goal to move towards a
single deployment mechanism that works across multiple platforms (Docker,
Metal, etc).
>
> I don't even know if this is feasible, but it may be worth a community
discussion. I'll kick something off.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
>
> Add index templates to metron-docker
> ------------------------------------
>
> Key: METRON-646
> URL: https://issues.apache.org/jira/browse/METRON-646
> Project: Metron
> Issue Type: Improvement
> Reporter: Kyle Richardson
> Assignee: Kyle Richardson
> Priority: Minor
>
> Customize the elasticsearch docker image:
> # to have the elasticsearch-head plugin installed as part of the image build
> # copy the es_templates into the image so they are available
> # deploy the templates on container start
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
