What is the Master Jira going to be?
On December 13, 2017 at 14:36:50, Ryan Merriman (merrim...@gmail.com) wrote: I am going to start the process of creating Jiras out of these initial requirements. I agree with them and think they are a good starting point. Feel free to join in at anytime and add/change/remove requirements as needed. I will update the thread once I have the initial Jiras created and we can go from there. On Mon, Dec 11, 2017 at 4:10 PM, Ryan Merriman <merrim...@gmail.com> wrote: > The purpose of this discussion is map out what is required to get the POC > started with https://github.com/apache/metron/pull/858 into master. > > The following features were added in the previously mentioned PR: > > - Dockerfile for Metron REST > - Dockerfile for Metron UIs > - Docker Compose application including Metron images, Elasticsearch, > Kafka, Zookeeper > - Modified travis file that manages the Docker environment and runs > the e2e tests as part of the build > - Maven pom.xml that installs all the required assets into the Docker > e2e module > - Modified metron-alerts pom.xml that allows e2e tests to be run > through Maven > - An example integration test that has been converted to use the new > infrastructure > > Here are the initial features proposed for acceptance into master: > > - All e2e and integration tests run on common infrastructure. > - All e2e and integration tests are run automatically in the Travis > build. > - All e2e and integration tests run repeatably and reliably in the > Travis build. > - Debugging options are available and documented. > - The new infra and how to interact with it is documented. > - Old infrastructure removed (anything unused or commented out is > deleted, instead of staying). > > Are there other requirements people want to add to this list? > > > >
