metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Allen <>
Subject [Discuss] Direction of metron-docker
Date Sun, 05 Feb 2017 21:22:53 GMT
Where is the `metron-docker` code base headed? What do we want that to be?
How will it work with the other deployment mechanisms?

So far a lot of work has gone into creating the Ambari MPack and we have
been moving away from the legacy Ansible deployments.  I have a limited
understanding of the `metron-docker` stuff, but it seems to introduce a
third deployment mechanism via the Docker files.

Is there no way to leverage the existing deployment paths for

---------- Forwarded message ----------
From: nickwallen <>
Date: Sun, Feb 5, 2017 at 4:09 PM
Subject: [GitHub] incubator-metron issue #441: METRON-646: Add index
templates to metron-docke...

Github user nickwallen commented on the issue:

    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.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message