[
https://issues.apache.org/jira/browse/METRON-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281888#comment-16281888
]
ASF GitHub Bot commented on METRON-1344:
----------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/858
Ok, I'm going to try running through some things.
One point, and I will admit this just may be me:
I see the same problem with this as I had with the original docker stuff.
The list of instructions for initial use is there, but I don't quite
understand how after this initial use I would go back to this setup and use it
day to day. Do these steps need to happen every time?
Is there a way to script this such that there is an
init_metron_testing_docker, start_metron_testing_docker
shutdown_metron_testing_docker etc?
> Externalize the infrastructural components using integration tests
> ------------------------------------------------------------------
>
> Key: METRON-1344
> URL: https://issues.apache.org/jira/browse/METRON-1344
> Project: Metron
> Issue Type: Improvement
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
>
> As we move towards adding the Alerts UI e2e test to our continuous build, we
> need to remove the dependence on vagrant full dev and provide equivalent
> infrastructure within Travis. This will include all the services that the
> e2e tests depend on including Kafka, Zookeeper, Elasticsearch (possibly
> HBase), and Metron REST.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
