metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Leet <justinjl...@gmail.com>
Subject Re: [DISCUSS] Integration/e2e test infrastructure requirements
Date Thu, 14 Dec 2017 14:07:19 GMT
I think this covers the main things I want to see from a first cut (which
shouldn't be surprising to anyone who followed the PR thread).

The potential follow-on I'd like to see, is having the integration + e2e
tests handled during the maven integration test phase with the failsafe
plugin, instead of just being unit tests. Having said that, it's definitely
low priority, even once this stuff is complete.

On Wed, Dec 13, 2017 at 6:24 PM, Otto Fowler <ottobackwards@gmail.com>
wrote:

> Awesome Ryan!
> Have you thought about confluence?
>
>
> On December 13, 2017 at 18:11:39, Ryan Merriman (merrimanr@gmail.com)
> wrote:
>
> I took a first pass at adding tasks and will continue adding more as I
> think of them. I will wait for feedback on which modules to include before
> I add all those (only added metron-elasticsearch for now). I left all but
> a couple unassigned so that anyone can pick up a task if they want.
>
> On Wed, Dec 13, 2017 at 4:41 PM, Ryan Merriman <merrimanr@gmail.com>
> wrote:
>
> > Jira is here: https://issues.apache.org/jira/browse/METRON-1352. I am
> > starting to create sub-tasks based on the requirements outlined above and
> > included in that Jira description.
> >
> > I am compiling a list of modules that we'll need to convert to the
> testing
> > infrastructure. Based on imports of ComponentRunner, I get these modules:
> >
> > - metron-elasticsearch
> > - metron-enrichment
> > - metron-indexing
> > - metron-integration-test
> > - metron-maas-service
> > - metron-management
> > - metron-pcap-backend
> > - metron-profiler
> > - metron-rest
> > - metron-solr
> >
> > I am planning on creating sub-tasks for each of these. I know that
> > metron-common should also be converted because it uses the Zookeeper in
> > memory server but doesn't use ComponentRunner to manage it. Are there
> > other modules like this that you know of?
> >
> > On Wed, Dec 13, 2017 at 2:44 PM, Otto Fowler <ottobackwards@gmail.com>
> > wrote:
> >
> >> Same as the feature branch name? I just want to find it and set a watch
> >> on it ;)
> >>
> >>
> >> On December 13, 2017 at 15:29:00, Ryan Merriman (merrimanr@gmail.com)
> >> wrote:
> >>
> >> I'm open to ideas. What do you think the title should be?
> >>
> >> On Wed, Dec 13, 2017 at 2:13 PM, Otto Fowler <ottobackwards@gmail.com>
> >> wrote:
> >>
> >> > What is the Master Jira going to be?
> >> >
> >> >
> >> >
> >> > On December 13, 2017 at 14:36:50, Ryan Merriman (merrimanr@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 <merrimanr@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?
> >> > >
> >> > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
>

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