My apologies for not weighing in sooner.

Github: https://github.com/apache/incubator-metron/releases/tag/Metron_0.1BETA_rc5

You don’t need to include this. Github is just a mirror. The important repository is the git repo hosted by the ASF.

With a Git hash:
443ad7baa2ce5c3127a9691c7d45b7a4a92e257b

Good job. All releases should be traceable back to a specific commit. Tags can be moved in git, Commit SHAs not so much.


The following are instructions for verifying the build.

Those instructions should probably be part of the documentation rather than a release vote. 

Apache releases source code, not compiled/packaged software. That code can be buggy as hell. It doesn’t matter. Quality of the resulting executable software is a secondary concern. The most important point is that the *source* is clean from a licensing perspecitve (LICENSE/NOTICE, Incubator DISCLAIMER, Apache headers in source, all source tied to a grant/(I)(C)CLA, etc.).

Another thing missing from this VOTE are the signatures, checksums, and pointer to the KEYS file that includes the signature of the persons signing the release. Without these, it’s impossible to verify a release.

You can find more information here: [1] [2]

-Taylor

[1] http://incubator.apache.org/guides/releasemanagement.html
[2] http://www.apache.org/dev/release.html


On Mar 22, 2016, at 6:56 PM, James Sirota <jsirota@hortonworks.com> wrote:


A tag has been created for Metron_0.1BETA_RC5

Github: https://github.com/apache/incubator-metron/releases/tag/Metron_0.1BETA_rc5
Apache: https://git-wip-us.apache.org/repos/asf?p=incubator-metron.git;a=shortlog;h=refs/tags/Metron_0.1BETA_rc5

With a Git hash:
443ad7baa2ce5c3127a9691c7d45b7a4a92e257b

The code is staged at http://home.apache.org/~jsirota/metron/Metron_0.1BETA_RC/RC_5/

The following are instructions for verifying the build.

Step 1 – Build Metron

cd incubator-metron/metron-streaming/
mvn apache-rat:check && cd metron-streaming && mvn clean integration-test && cd ..

Verify that all tests are passing

Step 2 – Deploy metron as a single VM via vagrant and ansible

cd deployment/vagrant/singlenode-vagrant
vagrant plugin install vagrant-hostmanager
vagrant up

For a more complete set of instructions refer to:
https://github.com/apache/incubator-metron/tree/master/deployment

Verify metron is working:
- Check Ambari to make sure all the services are up by going to ambari in a browser at http://node1:8080
- Check Storm to make sure all the topologies are up
     From Ambari navigate to Storm -> Quick Links -> Storm UI
- Check that the enrichment topology has emitted some data (could take a few minutes to show up in the Storm UI)
- Check indexes to make sure indexing is done correctly and data is visualized in Kibana in a browser at http://node1:5000
- Check that some data is written into HDFS for at least one of the data sources
     Look in HDFS under /apps/metron/enrichment/indexed/yaf_doc|bro_doc|snort_doc
     This can be done from the browser by going to http://node:50070/explorer.html#/apps/metron/enrichment/indexed

Step 3 (optional) – Verify AWS Multi-Node Deploy with Ansible
cd deployment/amazon-ec2
ansible-playbook -i ec2.py playbook.yml

For a more complete set of instructions refer to:
https://github.com/apache/incubator-metron/tree/master/deployment

To verify the working build go through the same verifications as in Step2, but on AWS.  Reference playbook.yml for location of the services.
Ambari-master contains Ambari, web contains Kibana and sensors.

Please vote +1 if you approve and –1 if you do not approve.  Also, please indicate if your
vote is binding