Semi-related to this, I would like to see METRON-902 <https://issues.apache.org/jira/browse/METRON-902> make it into 0.4.0, as it is a fix for a current indexing problem with bro logs in ES.
Jon On Fri, Apr 28, 2017 at 2:20 PM Matt Foley <[email protected]> wrote: > I’ve opened https://issues.apache.org/jira/browse/METRON-905 to fix both > the default i/f and the square brackets issue. > > On 4/28/17, 10:30 AM, "Matt Foley" <[email protected]> wrote: > > I’m happy to re-spin with a default of binding to all interfaces > (0.0.0.0) > With that single setting, are the square brackets still needed? > Thanks, > --Matt > > On 4/28/17, 6:22 AM, "Nick Allen" <[email protected]> wrote: > > -1 binding > > I agree with you Anand. It should work out-of-the-box. The fix > is simple. > > On Fri, Apr 28, 2017 at 6:56 AM, Anand Subramanian < > [email protected]> wrote: > > > -1 (non-binding) > > > > Validated on a 12-node openstack CentOS 7 setup. > > > > - Ran 'mvn clean package' [PASS] > > - Able to build RPMs [PASS] > > - Cluster deployment [PASS] > > - ES services were getting killed - https://issues.apache.org/ > > jira/browse/METRON-897 > > > > With the workaround provided in METRON-897, I was able to > proceed and > > subsequently validate the following to be working: > > > > * Bro, YAF and snort able to ingest from respective kafka topics > and write > > indices [PASS] > > * Able to add squid telemetry, ingest from kafka topic and write > indices > > [PASS] > > * Metron YAF Zeppelin dashboard with sample ingested YAF data > [PASS] > > > > Please advice if METRON-897 is considered a release blocker, or > would we > > be okay with documenting it as a known issue? My vote would be a > +1 > > (non-binding) in case we decide to release note this issue. > > > > Regards, > > Anand > > > > > > > > > > On 4/28/17, 4:12 PM, "Mohan Venkateshaiah" < > [email protected]> > > wrote: > > > > >+1 (non-binding) > > > > > >completed the below testing on the build > > > > > >1. Built metron 0.4.0 > > >2. Deployed metron vagrant full-dev-platform > > >3. Verified metron is working by checking Ambari, Storm , > indexing and > > data written to HDFS. > > >4. Added new squid telemetry > > >5. Created new ‘whois’ enrichment and validated. > > > > > >Thanks > > >Mohan DV > > >On 4/28/17, 9:55 AM, "Matt Foley" <[email protected]> wrote: > > > > > > Colleagues, > > > > > > This is a call to vote on the second release candidate for > Apache > > Metron 0.4.0 (Note: not incubating any more!) > > > Full list of changes in this release, compared to 0.3.1: > > > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.4. > > 0-RC2/RELEASE_NOTES > > > > > > The tag/commit to be voted upon is: > > > apache-metron-0.4.0-rc2 > > > This is identical to “master” as of the evening of 27 > April. > > > > > > The source archive being voted upon can be found here: > > > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.4. > > 0-RC2/apache-metron-0.4.0-rc2.tar.gz > > > > > > Other release files, signatures and digests can be found > here: > > > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.4.0-RC2/ > > > > > > The release artifacts are signed with the following key: > > > 7854 36A7 8258 6B71 829C 67A0 4169 AA27 ECB3 1663 in > > > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.4. > > 0-RC2/KEYS > > > > > > Please vote on releasing this package as Apache Metron 0.4.0 > > > > > > When voting, please list the actions taken to verify the > release. > > > > > > Recommended build validation and verification instructions > are posted > > here: > > > https://cwiki.apache.org/confluence/display/METRON/ > > Verifying+Builds > > > > > > This vote will be open for at least 72 hours. > > > Please vote as follows: > > > +1 Release this package as Apache Metron 0.4.0 > > > 0 No opinion > > > -1 Do not release this package because... > > > > > > Thanks everybody for your on-going contributions to the > Metron > > project! > > > --Matt > > > (Release Manager) > > > > > > > > > > > > > > > > > > > > > > > > > -- Jon
