You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@metron.apache.org by James Sirota <js...@hortonworks.com> on 2016/03/22 23:56:49 UTC

[VOTE] Release of Metron_0.1BETA_rc5

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

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by David Lyle <dl...@gmail.com>.

+1 (non-binding) to release.

Ran both singlenode vagrant and ec2.

I did notice the following:

pycapa needs to be restarted after initial startup- it seems to be timing
out on initial startup. On restart it stays up.

Here's the stack trace:

WARNING: No route found for IPv6 destination :: (no default route?)

No handlers could be found for logger "kafka"

Traceback (most recent call last):

  File "/usr/local/pycapa/pycapa/pycapa_cli.py", line 96, in <module>

    main()

  File "/usr/local/pycapa/pycapa/pycapa_cli.py", line 93, in main

    sniff(iface=args.interface, store=0, prn=produce_callback)

  File "/usr/lib/python2.6/site-packages/scapy/sendrecv.py", line 595, in
sniff

    r = prn(p)

  File "/usr/local/pycapa/pycapa/pycapa_cli.py", line 51, in
produce_callback

    res = producer.send(topic, packet_count, msg)

  File "/usr/lib/python2.6/site-packages/kafka/producer.py", line 311, in
send

    return self.send_messages(topic, partition, msg)

  File "/usr/lib/python2.6/site-packages/kafka/producer.py", line 188, in
send_messages

    timeout=self.ack_timeout)

  File "/usr/lib/python2.6/site-packages/kafka/client.py", line 312, in
send_produce_request

    resps = self._send_broker_aware_request(payloads, encoder, decoder)

  File "/usr/lib/python2.6/site-packages/kafka/client.py", line 179, in
_send_broker_aware_request

    raise FailedPayloadsError(failed_payloads)

kafka.common.FailedPayloadsError: [ProduceRequest(topic='pcap',
partition=0, messages=[Message(magic=0, attributes=0, key=None,
value='\xd4\xc3\xb2\xa1\x02\x00\x04\x00\x00\x00\x00\x00\x00\x00\x00\x00\xff\xff\x00\x00\x01\x00\x00\x00\xb4x\xf2V\x97$\x07\x00\x89\x00\x00\x00\x89\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x08\x00E\x00\x00{\x08\xc2\x00\x00\x80\x11\x9b\xbe\xc0\xa8\x8a\x9e\xc0\xa8\x8a\x02\xea\xae\x005\x00g\xf8\tG\xae\x01\x00\x00\x01\x00\x00\x00\x00\x00\x00\x06va872g\x06g90e1h\x02b8\x07642b63u\x06j985a2\x04v33e\x0237\x07pa269cc\x0ce8mfzdgrf7g0\rgroupprograms\x02in\x00\x00\x01\x00\x01')])]



On Tue, Mar 22, 2016 at 6:56 PM, James Sirota <js...@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
>
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by Hakkı Hakan Akansel <ha...@gmail.com>.

All components works well, however if you restart the single-node local
machine, all services are stopped and you should start these services.

On Thu, Mar 24, 2016 at 5:56 PM, Nick Allen <ni...@nickallen.org> wrote:

> +1 (non-binding)
>
> Fully functioning in Amazon EC2 and local Virtualbox/Vagrant-base
> environments.
>
> On Tue, Mar 22, 2016 at 6:56 PM, James Sirota <js...@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
> >
> >
>
>
> --
> Nick Allen <ni...@nickallen.org>
>



-- 


*Hakki Hakan Akansel*
*Eskisehir Osmangazi Üniversitesi*
*Bilgisayar Mühendisliği *
*Elektrik - Elektronik Mühendisliği (CAP)*

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by Nick Allen <ni...@nickallen.org>.

+1 (non-binding)

Fully functioning in Amazon EC2 and local Virtualbox/Vagrant-base
environments.

On Tue, Mar 22, 2016 at 6:56 PM, James Sirota <js...@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
>
>


-- 
Nick Allen <ni...@nickallen.org>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by James Sirota <js...@hortonworks.com>.

+1 (Binding)  

I verified the release and everything works 

Thanks,
James 





On 3/28/16, 5:23 PM, "James Sirota" <js...@hortonworks.com> wrote:

>Hi Taylor,
>
>The keys file is included in the staging directory in Apache
>
>http://home.apache.org/~jsirota/metron/Metron_0.1BETA_RC/RC_5/KEYS
>
>I also provided the PGP electronic signature and the SHA1 hash::
>
>http://home.apache.org/~jsirota/metron/Metron_0.1BETA_RC/RC_5/incubator-metron-Metron_0.1BETA_rc5.tar.gz.asc
>
>http://home.apache.org/~jsirota/metron/Metron_0.1BETA_RC/RC_5/incubator-metron-Metron_0.1BETA_rc5.tar.gz.sha
>
>Thanks,
>James
>
>From: "P. Taylor Goetz" <pt...@gmail.com>>
>Reply-To: <de...@metron.incubator.apache.org>>
>Date: Monday, March 28, 2016 at 5:17 PM
>To: <de...@metron.incubator.apache.org>>
>Subject: Re: [VOTE] Release of Metron_0.1BETA_rc5
>
>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 <js...@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
>
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by "P. Taylor Goetz" <pt...@gmail.com>.

Hi James,

Thanks for pointing that out, I missed that because it’s common practice to explicitly point to the release artifacts.

Here’s a template I use for release votes:
-----------------------------------------------
This is a call to vote on releasing Apache $PROJECT $VERSION

Full list of changes in this release:

[Link to CHANGELOG]

The tag/commit to be voted upon is $GIT_TAG_NAME:

[Link to commit SHA on git-wip-us.apache.org]

The source archive being voted upon can be found here:

[Link to source tarball on dist.apache.org]

Other release files, signatures and digests can be found here:

[Link to release dir on dist.apache.org]

The release artifacts are signed with the following key:

[Link to KEYS file on git-wip-us.apache.org]

The Nexus staging repository for this release is:

[Link to staging repo on repository.apache.org]

Please vote on releasing this package as $PROJECT $VERSION.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as $PROJECT $VERSION
[ ]  0 No opinion
[ ] -1 Do not release this package because...
-----------------------------------------------

Getting IPMC members to vote on a release is notoriously hard. The idea behind the template is to make it as easy as possible for IPMC members to verify a release.

Note that hosting the release artifacts on home.apache.org <http://home.apache.org/> is now discouraged (someone will almost certainly bring this up in the IPMC vote). They should be hosted on dist.apache.org. You can stage them there by committing them to subversion at the following URL:

https://dist.apache.org/repos/dist/dev/incubator/metron <https://dist.apache.org/repos/dist/dev/incubator/metron>

(You will need to `svn mkdir metron` since it doesn’t exist yet.)

Another nit that may come up is the naming of the release. The preferred naming would be “apache-metron-incubating” or “metron-incubating”.

If you can address some of these points you will probably have a better chance of having a release approved by the IPMC.

-Taylor

> On Mar 28, 2016, at 8:23 PM, James Sirota <js...@hortonworks.com> wrote:
> 
> Hi Taylor,
> 
> The keys file is included in the staging directory in Apache
> 
> http://home.apache.org/~jsirota/metron/Metron_0.1BETA_RC/RC_5/KEYS
> 
> I also provided the PGP electronic signature and the SHA1 hash::
> 
> http://home.apache.org/~jsirota/metron/Metron_0.1BETA_RC/RC_5/incubator-metron-Metron_0.1BETA_rc5.tar.gz.asc
> 
> http://home.apache.org/~jsirota/metron/Metron_0.1BETA_RC/RC_5/incubator-metron-Metron_0.1BETA_rc5.tar.gz.sha
> 
> Thanks,
> James
> 
> From: "P. Taylor Goetz" <pt...@gmail.com>>
> Reply-To: <de...@metron.incubator.apache.org>>
> Date: Monday, March 28, 2016 at 5:17 PM
> To: <de...@metron.incubator.apache.org>>
> Subject: Re: [VOTE] Release of Metron_0.1BETA_rc5
> 
> 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 <js...@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
> 
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by James Sirota <js...@hortonworks.com>.

Hi Taylor,

The keys file is included in the staging directory in Apache

http://home.apache.org/~jsirota/metron/Metron_0.1BETA_RC/RC_5/KEYS

I also provided the PGP electronic signature and the SHA1 hash::

http://home.apache.org/~jsirota/metron/Metron_0.1BETA_RC/RC_5/incubator-metron-Metron_0.1BETA_rc5.tar.gz.asc

http://home.apache.org/~jsirota/metron/Metron_0.1BETA_RC/RC_5/incubator-metron-Metron_0.1BETA_rc5.tar.gz.sha

Thanks,
James

From: "P. Taylor Goetz" <pt...@gmail.com>>
Reply-To: <de...@metron.incubator.apache.org>>
Date: Monday, March 28, 2016 at 5:17 PM
To: <de...@metron.incubator.apache.org>>
Subject: Re: [VOTE] Release of Metron_0.1BETA_rc5

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 <js...@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

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by "P. Taylor Goetz" <pt...@gmail.com>.

My apologies for not weighing in sooner.

> Github: https://github.com/apache/incubator-metron/releases/tag/Metron_0.1BETA_rc5 <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 <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 <js...@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
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by "P. Taylor Goetz" <pt...@gmail.com>.

For minified JavaScript or even things like images that can’t have license headers, you can put the license information in your LICENSE file.

Here’s a snippet from Storm’s LICENSE file for an image:

-------------------------------------------------------------------------
For statistic image:

./storm-core/src/ui/public/images/statistic.png

Copyright (c) 2015 Github, Inc.


Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:


The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.


THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
-------------------------------------------------------------------------

-Taylor

> On Mar 29, 2016, at 3:03 PM, Casey Stella <ce...@gmail.com> wrote:
> 
> Thanks Taylor,
> 
> Regarding the bundled dependencies.  We are bundling minified versions of
> those javascript dependencies, so they're not coming along with the license
> files or anything.  I can place the license files in a directory next to
> them, but we're not capturing the source distribution, is that ok?  Or do I
> need to track down the full package?
> 
> Casey
> 
> On Tue, Mar 29, 2016 at 2:05 PM, P. Taylor Goetz <pt...@gmail.com> wrote:
> 
>> Looking at the actual release I found the following:
>> 
>> There are multiple LICENSE files:
>> $ find ./ -name LICENSE
>> .//LICENSE
>> .//metron-streaming/LICENSE
>> .//metron-ui/LICENSE
>> 
>> There’s also ./bro-plugin-kafka/COPYING
>> 
>> You should probably remove the extra LICENSE files and keep the top level
>> one.
>> 
>> The NOTICE file contains the following text:
>> 
>> "Portions of this software were developed at Cisco Systems and have been
>> kindly donated to the Apache Software Foundation.”
>> 
>> That is not the typical format and if not necessary should be removed. See
>> [1] and [2]. If necessary it should read:
>> 
>> "This product includes software developed by Cisco Systems (
>> http://www.cisco.com)
>> Copyright (c) 2014 Cisco Systems.
>> 
>> The main LICENSE file contains entries such as this:
>> 
>> "This product bundles filesaver 2013-01-23, which is available under a
>> "MIT" license.”
>> 
>> Those entries should also include a pointer to the file(s) containing that
>> license, e.g. “For details, see path/to/dependency”. See [3].
>> 
>> The website source code (./site) is included in the release, but excluded
>> from the RAT check. If included in the release, the same licensing rules
>> apply as they do to the rest of the source code. The same thing applies to
>> “metron-ui” I noticed at least one file (app.js) there that’s missing a
>> header. There are also a bunch of .ldif files that are missing headers.
>> 
>> You may want to consider addressing some of these issues before moving on
>> to an IPMC vote.
>> 
>> -Taylor
>> 
>> [1] http://www.apache.org/dev/licensing-howto.html
>> [2] http://www.apache.org/dev/licensing-howto.html#mod-notice
>> [3] http://www.apache.org/dev/licensing-howto.html#permissive-deps
>> 
>> On Mar 22, 2016, at 6:56 PM, James Sirota <js...@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
>> 
>> 
>>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by Casey Stella <ce...@gmail.com>.

Thanks Taylor,

Regarding the bundled dependencies.  We are bundling minified versions of
those javascript dependencies, so they're not coming along with the license
files or anything.  I can place the license files in a directory next to
them, but we're not capturing the source distribution, is that ok?  Or do I
need to track down the full package?

Casey

On Tue, Mar 29, 2016 at 2:05 PM, P. Taylor Goetz <pt...@gmail.com> wrote:

> Looking at the actual release I found the following:
>
> There are multiple LICENSE files:
> $ find ./ -name LICENSE
> .//LICENSE
> .//metron-streaming/LICENSE
> .//metron-ui/LICENSE
>
> There’s also ./bro-plugin-kafka/COPYING
>
> You should probably remove the extra LICENSE files and keep the top level
> one.
>
> The NOTICE file contains the following text:
>
> "Portions of this software were developed at Cisco Systems and have been
> kindly donated to the Apache Software Foundation.”
>
> That is not the typical format and if not necessary should be removed. See
> [1] and [2]. If necessary it should read:
>
> "This product includes software developed by Cisco Systems (
> http://www.cisco.com)
> Copyright (c) 2014 Cisco Systems.
>
> The main LICENSE file contains entries such as this:
>
> "This product bundles filesaver 2013-01-23, which is available under a
> "MIT" license.”
>
> Those entries should also include a pointer to the file(s) containing that
> license, e.g. “For details, see path/to/dependency”. See [3].
>
> The website source code (./site) is included in the release, but excluded
> from the RAT check. If included in the release, the same licensing rules
> apply as they do to the rest of the source code. The same thing applies to
> “metron-ui” I noticed at least one file (app.js) there that’s missing a
> header. There are also a bunch of .ldif files that are missing headers.
>
> You may want to consider addressing some of these issues before moving on
> to an IPMC vote.
>
> -Taylor
>
> [1] http://www.apache.org/dev/licensing-howto.html
> [2] http://www.apache.org/dev/licensing-howto.html#mod-notice
> [3] http://www.apache.org/dev/licensing-howto.html#permissive-deps
>
> On Mar 22, 2016, at 6:56 PM, James Sirota <js...@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
>
>
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by "P. Taylor Goetz" <pt...@gmail.com>.

Looking at the actual release I found the following:

There are multiple LICENSE files:
$ find ./ -name LICENSE
.//LICENSE
.//metron-streaming/LICENSE
.//metron-ui/LICENSE

There’s also ./bro-plugin-kafka/COPYING

You should probably remove the extra LICENSE files and keep the top level one.

The NOTICE file contains the following text:

"Portions of this software were developed at Cisco Systems and have been kindly donated to the Apache Software Foundation.”

That is not the typical format and if not necessary should be removed. See [1] and [2]. If necessary it should read:

"This product includes software developed by Cisco Systems (http://www.cisco.com)
Copyright (c) 2014 Cisco Systems.

The main LICENSE file contains entries such as this:

"This product bundles filesaver 2013-01-23, which is available under a "MIT" license.”

Those entries should also include a pointer to the file(s) containing that license, e.g. “For details, see path/to/dependency”. See [3].

The website source code (./site) is included in the release, but excluded from the RAT check. If included in the release, the same licensing rules apply as they do to the rest of the source code. The same thing applies to “metron-ui” I noticed at least one file (app.js) there that’s missing a header. There are also a bunch of .ldif files that are missing headers.

You may want to consider addressing some of these issues before moving on to an IPMC vote.

-Taylor

[1] http://www.apache.org/dev/licensing-howto.html <http://www.apache.org/dev/licensing-howto.html>
[2] http://www.apache.org/dev/licensing-howto.html#mod-notice <http://www.apache.org/dev/licensing-howto.html#mod-notice>
[3] http://www.apache.org/dev/licensing-howto.html#permissive-deps

> On Mar 22, 2016, at 6:56 PM, James Sirota <js...@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
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by Casey Stella <ce...@gmail.com>.

+1, non-binding

On Tue, Mar 22, 2016 at 6:56 PM, James Sirota <js...@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
>
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by Billie Rinaldi <bi...@apache.org>.

It's optional. Here are the instructions for publishing maven artifacts:
http://www.apache.org/dev/publishing-maven-artifacts.html

On Wed, Mar 30, 2016 at 8:52 AM, Casey Stella <ce...@gmail.com> wrote:

> Taylor, I noticed that you have uploading to repository.apache.org in the
> template for the release vote.  First, is that strictly required?  Second,
> if so, are there instructions?  I'm having some problems uploading the
> bundle created by the mvn repository plugin to a staging repo due to a
> missing release profile (and I can't figure out where I might be able to
> create such a thing..perhaps I need different or more karma for that sort
> of thing?)
>
> Casey
>
> On Tue, Mar 29, 2016 at 10:03 PM, P. Taylor Goetz <pt...@gmail.com>
> wrote:
>
> > Okay, so you are using gitpubsub...
> >
> > To remove the website from the releas, the two easiest options I can
> think
> > of are:
> >
> > 1. Just exclude the site directory from the source release.
> > 2. Create a new, bare branch (e.g. "metron-site"), move the site content
> > there, and ask infra to point to that branch for website publishing.
> >
> > -Taylor
> >
> > > On Mar 29, 2016, at 7:57 PM, Casey Stella <ce...@gmail.com> wrote:
> > >
> > > We are currently generating the site with jekyll and infra has
> something
> > > setup that will pull the site from git.
> > >
> > > Casey
> > >
> > >> On Tue, Mar 29, 2016 at 7:55 PM, P. Taylor Goetz <pt...@gmail.com>
> > wrote:
> > >>
> > >> Yeah, I think that should cover it.
> > >>
> > >> In terms of licensing issues with the website code, I would recommend
> > >> excluding it from the release. If it's not vital to building the
> metron
> > >> runtime components, it doesn't need to be in a release.
> > >>
> > >> How are you currently generating and publishing the website?
> Svnpubsub?
> > >>
> > >> -Taylor
> > >>
> > >>>> On Mar 29, 2016, at 5:36 PM, Billie Rinaldi <bi...@apache.org>
> > wrote:
> > >>>>
> > >>>> On Tue, Mar 29, 2016 at 12:46 PM, Casey Stella <ce...@gmail.com>
> > >> wrote:
> > >>>>
> > >>>> Regarding the use of effective_tld_names.dat, it is in use currently
> > in
> > >> the
> > >>>> Whois enrichment adapter (for stripping top level domains from
> > domains),
> > >>>> but that adapter is not turned on in the tech preview.  That being
> > said,
> > >>>> it's likely we will want to use that file in the future.  Since this
> > is
> > >> a
> > >>>> reference file and the reason for the binary-only exclusion is "By
> > >>>> including only the object/binary form, there is less exposed surface
> > >> area
> > >>>> of the third-party work from which a work might be derived; this
> > >> addresses
> > >>>> the second guiding principle of this policy.", it would seem that
> its
> > >>>> inclusion as a piece of reference data lessens the exposed surface
> > area
> > >>>> from which a work might be derived, no?
> > >>>
> > >>> I read that part as saying that it's only okay to include the binary
> > >>> version; but since this is textual data there is no binary version of
> > >> these
> > >>> files that we could include.  However, I missed this part on my first
> > >> read:
> > >>> "For small amounts of source that is directly consumed by the ASF
> > product
> > >>> at runtime in source form, and for which that source is unmodified
> and
> > >>> unlikely to be changed anyway (say, by virtue of being specified by a
> > >>> standard), inclusion of appropriately labeled source is also
> permitted.
> > >> An
> > >>> example of this is the web-facesconfig_1_0.dtd, whose inclusion is
> > >> mandated
> > >>> by the JSR 127: JavaServer Faces specification."
> > >>>
> > >>> So it sounds like we could argue that these 3 files (which are all
> > >>> identical) are a small amount of source, and we will be allowed to
> > >> include
> > >>> them with an appropriate reference in our LICENSE **as long as we
> never
> > >>> modify the effective_tld_names.dat files**.
> > >>>
> > >>>
> > >>>>
> > >>>> Casey
> > >>>>
> > >>>>> On Tue, Mar 29, 2016 at 2:55 PM, Billie Rinaldi <billie@apache.org
> >
> > >> wrote:
> > >>>>>
> > >>>>> These files have Mozilla Public License, which has an unusual
> policy
> > >> that
> > >>>>> says we should only include them in binary form (!) -- see
> > >>>>> http://www.apache.org/legal/resolved.html#category-b.  Can we get
> > rid
> > >> of
> > >>>>> them?
> > >>
> > metron-streaming/Metron-Common/src/test/resources/effective_tld_names.dat
> > >>
> >
> metron-streaming/Metron-MessageParsers/src/test/resources/effective_tld_names.dat
> > >>
> >
> metron-streaming/Metron-Topologies/src/main/resources/effective_tld_names.dat
> > >>>>>
> > >>>>> The files at metron-ui/lib/public/font/* seem to have SIL Open Font
> > >>>> License
> > >>>>> (https://github.com/FortAwesome/Font-Awesome#license), which has
> the
> > >>>> same
> > >>>>> restriction, but they're okay since they're binary.  We need to add
> > >> their
> > >>>>> info to our LICENSE.
> > >>>>>
> > >>>>> - checksums and signature are valid -- next time include a md5
> > >> signature
> > >>>>> - DISCLAIMER is correct -- file name should include "incubating"
> but
> > >>>>> "incubator" is close
> > >>>>> - no binaries in source tarball
> > >>>>> - build is successful
> > >>>>>
> > >>>>> Billie
> > >>>>>
> > >>>>> On Tue, Mar 22, 2016 at 3: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
> > >>
> >
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by Casey Stella <ce...@gmail.com>.

Taylor, I noticed that you have uploading to repository.apache.org in the
template for the release vote.  First, is that strictly required?  Second,
if so, are there instructions?  I'm having some problems uploading the
bundle created by the mvn repository plugin to a staging repo due to a
missing release profile (and I can't figure out where I might be able to
create such a thing..perhaps I need different or more karma for that sort
of thing?)

Casey

On Tue, Mar 29, 2016 at 10:03 PM, P. Taylor Goetz <pt...@gmail.com> wrote:

> Okay, so you are using gitpubsub...
>
> To remove the website from the releas, the two easiest options I can think
> of are:
>
> 1. Just exclude the site directory from the source release.
> 2. Create a new, bare branch (e.g. "metron-site"), move the site content
> there, and ask infra to point to that branch for website publishing.
>
> -Taylor
>
> > On Mar 29, 2016, at 7:57 PM, Casey Stella <ce...@gmail.com> wrote:
> >
> > We are currently generating the site with jekyll and infra has something
> > setup that will pull the site from git.
> >
> > Casey
> >
> >> On Tue, Mar 29, 2016 at 7:55 PM, P. Taylor Goetz <pt...@gmail.com>
> wrote:
> >>
> >> Yeah, I think that should cover it.
> >>
> >> In terms of licensing issues with the website code, I would recommend
> >> excluding it from the release. If it's not vital to building the metron
> >> runtime components, it doesn't need to be in a release.
> >>
> >> How are you currently generating and publishing the website? Svnpubsub?
> >>
> >> -Taylor
> >>
> >>>> On Mar 29, 2016, at 5:36 PM, Billie Rinaldi <bi...@apache.org>
> wrote:
> >>>>
> >>>> On Tue, Mar 29, 2016 at 12:46 PM, Casey Stella <ce...@gmail.com>
> >> wrote:
> >>>>
> >>>> Regarding the use of effective_tld_names.dat, it is in use currently
> in
> >> the
> >>>> Whois enrichment adapter (for stripping top level domains from
> domains),
> >>>> but that adapter is not turned on in the tech preview.  That being
> said,
> >>>> it's likely we will want to use that file in the future.  Since this
> is
> >> a
> >>>> reference file and the reason for the binary-only exclusion is "By
> >>>> including only the object/binary form, there is less exposed surface
> >> area
> >>>> of the third-party work from which a work might be derived; this
> >> addresses
> >>>> the second guiding principle of this policy.", it would seem that its
> >>>> inclusion as a piece of reference data lessens the exposed surface
> area
> >>>> from which a work might be derived, no?
> >>>
> >>> I read that part as saying that it's only okay to include the binary
> >>> version; but since this is textual data there is no binary version of
> >> these
> >>> files that we could include.  However, I missed this part on my first
> >> read:
> >>> "For small amounts of source that is directly consumed by the ASF
> product
> >>> at runtime in source form, and for which that source is unmodified and
> >>> unlikely to be changed anyway (say, by virtue of being specified by a
> >>> standard), inclusion of appropriately labeled source is also permitted.
> >> An
> >>> example of this is the web-facesconfig_1_0.dtd, whose inclusion is
> >> mandated
> >>> by the JSR 127: JavaServer Faces specification."
> >>>
> >>> So it sounds like we could argue that these 3 files (which are all
> >>> identical) are a small amount of source, and we will be allowed to
> >> include
> >>> them with an appropriate reference in our LICENSE **as long as we never
> >>> modify the effective_tld_names.dat files**.
> >>>
> >>>
> >>>>
> >>>> Casey
> >>>>
> >>>>> On Tue, Mar 29, 2016 at 2:55 PM, Billie Rinaldi <bi...@apache.org>
> >> wrote:
> >>>>>
> >>>>> These files have Mozilla Public License, which has an unusual policy
> >> that
> >>>>> says we should only include them in binary form (!) -- see
> >>>>> http://www.apache.org/legal/resolved.html#category-b.  Can we get
> rid
> >> of
> >>>>> them?
> >>
> metron-streaming/Metron-Common/src/test/resources/effective_tld_names.dat
> >>
> metron-streaming/Metron-MessageParsers/src/test/resources/effective_tld_names.dat
> >>
> metron-streaming/Metron-Topologies/src/main/resources/effective_tld_names.dat
> >>>>>
> >>>>> The files at metron-ui/lib/public/font/* seem to have SIL Open Font
> >>>> License
> >>>>> (https://github.com/FortAwesome/Font-Awesome#license), which has the
> >>>> same
> >>>>> restriction, but they're okay since they're binary.  We need to add
> >> their
> >>>>> info to our LICENSE.
> >>>>>
> >>>>> - checksums and signature are valid -- next time include a md5
> >> signature
> >>>>> - DISCLAIMER is correct -- file name should include "incubating" but
> >>>>> "incubator" is close
> >>>>> - no binaries in source tarball
> >>>>> - build is successful
> >>>>>
> >>>>> Billie
> >>>>>
> >>>>> On Tue, Mar 22, 2016 at 3: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
> >>
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by "P. Taylor Goetz" <pt...@gmail.com>.

Okay, so you are using gitpubsub...

To remove the website from the releas, the two easiest options I can think of are:

1. Just exclude the site directory from the source release.
2. Create a new, bare branch (e.g. "metron-site"), move the site content there, and ask infra to point to that branch for website publishing.

-Taylor

> On Mar 29, 2016, at 7:57 PM, Casey Stella <ce...@gmail.com> wrote:
> 
> We are currently generating the site with jekyll and infra has something
> setup that will pull the site from git.
> 
> Casey
> 
>> On Tue, Mar 29, 2016 at 7:55 PM, P. Taylor Goetz <pt...@gmail.com> wrote:
>> 
>> Yeah, I think that should cover it.
>> 
>> In terms of licensing issues with the website code, I would recommend
>> excluding it from the release. If it's not vital to building the metron
>> runtime components, it doesn't need to be in a release.
>> 
>> How are you currently generating and publishing the website? Svnpubsub?
>> 
>> -Taylor
>> 
>>>> On Mar 29, 2016, at 5:36 PM, Billie Rinaldi <bi...@apache.org> wrote:
>>>> 
>>>> On Tue, Mar 29, 2016 at 12:46 PM, Casey Stella <ce...@gmail.com>
>> wrote:
>>>> 
>>>> Regarding the use of effective_tld_names.dat, it is in use currently in
>> the
>>>> Whois enrichment adapter (for stripping top level domains from domains),
>>>> but that adapter is not turned on in the tech preview.  That being said,
>>>> it's likely we will want to use that file in the future.  Since this is
>> a
>>>> reference file and the reason for the binary-only exclusion is "By
>>>> including only the object/binary form, there is less exposed surface
>> area
>>>> of the third-party work from which a work might be derived; this
>> addresses
>>>> the second guiding principle of this policy.", it would seem that its
>>>> inclusion as a piece of reference data lessens the exposed surface area
>>>> from which a work might be derived, no?
>>> 
>>> I read that part as saying that it's only okay to include the binary
>>> version; but since this is textual data there is no binary version of
>> these
>>> files that we could include.  However, I missed this part on my first
>> read:
>>> "For small amounts of source that is directly consumed by the ASF product
>>> at runtime in source form, and for which that source is unmodified and
>>> unlikely to be changed anyway (say, by virtue of being specified by a
>>> standard), inclusion of appropriately labeled source is also permitted.
>> An
>>> example of this is the web-facesconfig_1_0.dtd, whose inclusion is
>> mandated
>>> by the JSR 127: JavaServer Faces specification."
>>> 
>>> So it sounds like we could argue that these 3 files (which are all
>>> identical) are a small amount of source, and we will be allowed to
>> include
>>> them with an appropriate reference in our LICENSE **as long as we never
>>> modify the effective_tld_names.dat files**.
>>> 
>>> 
>>>> 
>>>> Casey
>>>> 
>>>>> On Tue, Mar 29, 2016 at 2:55 PM, Billie Rinaldi <bi...@apache.org>
>> wrote:
>>>>> 
>>>>> These files have Mozilla Public License, which has an unusual policy
>> that
>>>>> says we should only include them in binary form (!) -- see
>>>>> http://www.apache.org/legal/resolved.html#category-b.  Can we get rid
>> of
>>>>> them?
>> metron-streaming/Metron-Common/src/test/resources/effective_tld_names.dat
>> metron-streaming/Metron-MessageParsers/src/test/resources/effective_tld_names.dat
>> metron-streaming/Metron-Topologies/src/main/resources/effective_tld_names.dat
>>>>> 
>>>>> The files at metron-ui/lib/public/font/* seem to have SIL Open Font
>>>> License
>>>>> (https://github.com/FortAwesome/Font-Awesome#license), which has the
>>>> same
>>>>> restriction, but they're okay since they're binary.  We need to add
>> their
>>>>> info to our LICENSE.
>>>>> 
>>>>> - checksums and signature are valid -- next time include a md5
>> signature
>>>>> - DISCLAIMER is correct -- file name should include "incubating" but
>>>>> "incubator" is close
>>>>> - no binaries in source tarball
>>>>> - build is successful
>>>>> 
>>>>> Billie
>>>>> 
>>>>> On Tue, Mar 22, 2016 at 3: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
>>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by Casey Stella <ce...@gmail.com>.

Ok, I created a PR <https://github.com/apache/incubator-metron/pull/64>
with the changes mentioned in this thread:

   - Removed extraneous LICENSE files and COPYING files
   - Fixed the verbiage for the cisco contribution in the LICENSE file
   - Added link to the license files for the 3rd party bundled components
   under metron-ui/lib/public/vendor in the LICENSE file
   - Added inline licenses in the LICENSE file for the
      - fontawesome fonts
      - effective_tld_names.dat data file
      - bundled portions of kibana (where you saw the app.js without the
      header file)

We will exclude the site in the bundle for the next RC, which should happen
tomorrow.

On Tue, Mar 29, 2016 at 7:57 PM, Casey Stella <ce...@gmail.com> wrote:

> We are currently generating the site with jekyll and infra has something
> setup that will pull the site from git.
>
> Casey
>
> On Tue, Mar 29, 2016 at 7:55 PM, P. Taylor Goetz <pt...@gmail.com>
> wrote:
>
>> Yeah, I think that should cover it.
>>
>> In terms of licensing issues with the website code, I would recommend
>> excluding it from the release. If it's not vital to building the metron
>> runtime components, it doesn't need to be in a release.
>>
>> How are you currently generating and publishing the website? Svnpubsub?
>>
>> -Taylor
>>
>> > On Mar 29, 2016, at 5:36 PM, Billie Rinaldi <bi...@apache.org> wrote:
>> >
>> >> On Tue, Mar 29, 2016 at 12:46 PM, Casey Stella <ce...@gmail.com>
>> wrote:
>> >>
>> >> Regarding the use of effective_tld_names.dat, it is in use currently
>> in the
>> >> Whois enrichment adapter (for stripping top level domains from
>> domains),
>> >> but that adapter is not turned on in the tech preview.  That being
>> said,
>> >> it's likely we will want to use that file in the future.  Since this
>> is a
>> >> reference file and the reason for the binary-only exclusion is "By
>> >> including only the object/binary form, there is less exposed surface
>> area
>> >> of the third-party work from which a work might be derived; this
>> addresses
>> >> the second guiding principle of this policy.", it would seem that its
>> >> inclusion as a piece of reference data lessens the exposed surface area
>> >> from which a work might be derived, no?
>> >>
>> >
>> > I read that part as saying that it's only okay to include the binary
>> > version; but since this is textual data there is no binary version of
>> these
>> > files that we could include.  However, I missed this part on my first
>> read:
>> > "For small amounts of source that is directly consumed by the ASF
>> product
>> > at runtime in source form, and for which that source is unmodified and
>> > unlikely to be changed anyway (say, by virtue of being specified by a
>> > standard), inclusion of appropriately labeled source is also permitted.
>> An
>> > example of this is the web-facesconfig_1_0.dtd, whose inclusion is
>> mandated
>> > by the JSR 127: JavaServer Faces specification."
>> >
>> > So it sounds like we could argue that these 3 files (which are all
>> > identical) are a small amount of source, and we will be allowed to
>> include
>> > them with an appropriate reference in our LICENSE **as long as we never
>> > modify the effective_tld_names.dat files**.
>> >
>> >
>> >>
>> >> Casey
>> >>
>> >>> On Tue, Mar 29, 2016 at 2:55 PM, Billie Rinaldi <bi...@apache.org>
>> wrote:
>> >>>
>> >>> These files have Mozilla Public License, which has an unusual policy
>> that
>> >>> says we should only include them in binary form (!) -- see
>> >>> http://www.apache.org/legal/resolved.html#category-b.  Can we get
>> rid of
>> >>> them?
>> >>>
>> metron-streaming/Metron-Common/src/test/resources/effective_tld_names.dat
>> >>>
>> >>>
>> >>
>> metron-streaming/Metron-MessageParsers/src/test/resources/effective_tld_names.dat
>> >>>
>> >>>
>> >>
>> metron-streaming/Metron-Topologies/src/main/resources/effective_tld_names.dat
>> >>>
>> >>> The files at metron-ui/lib/public/font/* seem to have SIL Open Font
>> >> License
>> >>> (https://github.com/FortAwesome/Font-Awesome#license), which has the
>> >> same
>> >>> restriction, but they're okay since they're binary.  We need to add
>> their
>> >>> info to our LICENSE.
>> >>>
>> >>> - checksums and signature are valid -- next time include a md5
>> signature
>> >>> - DISCLAIMER is correct -- file name should include "incubating" but
>> >>> "incubator" is close
>> >>> - no binaries in source tarball
>> >>> - build is successful
>> >>>
>> >>> Billie
>> >>>
>> >>> On Tue, Mar 22, 2016 at 3: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
>> >>>>
>> >>>>
>> >>>
>> >>
>>
>
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by Casey Stella <ce...@gmail.com>.

We are currently generating the site with jekyll and infra has something
setup that will pull the site from git.

Casey

On Tue, Mar 29, 2016 at 7:55 PM, P. Taylor Goetz <pt...@gmail.com> wrote:

> Yeah, I think that should cover it.
>
> In terms of licensing issues with the website code, I would recommend
> excluding it from the release. If it's not vital to building the metron
> runtime components, it doesn't need to be in a release.
>
> How are you currently generating and publishing the website? Svnpubsub?
>
> -Taylor
>
> > On Mar 29, 2016, at 5:36 PM, Billie Rinaldi <bi...@apache.org> wrote:
> >
> >> On Tue, Mar 29, 2016 at 12:46 PM, Casey Stella <ce...@gmail.com>
> wrote:
> >>
> >> Regarding the use of effective_tld_names.dat, it is in use currently in
> the
> >> Whois enrichment adapter (for stripping top level domains from domains),
> >> but that adapter is not turned on in the tech preview.  That being said,
> >> it's likely we will want to use that file in the future.  Since this is
> a
> >> reference file and the reason for the binary-only exclusion is "By
> >> including only the object/binary form, there is less exposed surface
> area
> >> of the third-party work from which a work might be derived; this
> addresses
> >> the second guiding principle of this policy.", it would seem that its
> >> inclusion as a piece of reference data lessens the exposed surface area
> >> from which a work might be derived, no?
> >>
> >
> > I read that part as saying that it's only okay to include the binary
> > version; but since this is textual data there is no binary version of
> these
> > files that we could include.  However, I missed this part on my first
> read:
> > "For small amounts of source that is directly consumed by the ASF product
> > at runtime in source form, and for which that source is unmodified and
> > unlikely to be changed anyway (say, by virtue of being specified by a
> > standard), inclusion of appropriately labeled source is also permitted.
> An
> > example of this is the web-facesconfig_1_0.dtd, whose inclusion is
> mandated
> > by the JSR 127: JavaServer Faces specification."
> >
> > So it sounds like we could argue that these 3 files (which are all
> > identical) are a small amount of source, and we will be allowed to
> include
> > them with an appropriate reference in our LICENSE **as long as we never
> > modify the effective_tld_names.dat files**.
> >
> >
> >>
> >> Casey
> >>
> >>> On Tue, Mar 29, 2016 at 2:55 PM, Billie Rinaldi <bi...@apache.org>
> wrote:
> >>>
> >>> These files have Mozilla Public License, which has an unusual policy
> that
> >>> says we should only include them in binary form (!) -- see
> >>> http://www.apache.org/legal/resolved.html#category-b.  Can we get rid
> of
> >>> them?
> >>>
> metron-streaming/Metron-Common/src/test/resources/effective_tld_names.dat
> >>>
> >>>
> >>
> metron-streaming/Metron-MessageParsers/src/test/resources/effective_tld_names.dat
> >>>
> >>>
> >>
> metron-streaming/Metron-Topologies/src/main/resources/effective_tld_names.dat
> >>>
> >>> The files at metron-ui/lib/public/font/* seem to have SIL Open Font
> >> License
> >>> (https://github.com/FortAwesome/Font-Awesome#license), which has the
> >> same
> >>> restriction, but they're okay since they're binary.  We need to add
> their
> >>> info to our LICENSE.
> >>>
> >>> - checksums and signature are valid -- next time include a md5
> signature
> >>> - DISCLAIMER is correct -- file name should include "incubating" but
> >>> "incubator" is close
> >>> - no binaries in source tarball
> >>> - build is successful
> >>>
> >>> Billie
> >>>
> >>> On Tue, Mar 22, 2016 at 3: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
> >>>>
> >>>>
> >>>
> >>
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by "P. Taylor Goetz" <pt...@gmail.com>.

Yeah, I think that should cover it.

In terms of licensing issues with the website code, I would recommend excluding it from the release. If it's not vital to building the metron runtime components, it doesn't need to be in a release.

How are you currently generating and publishing the website? Svnpubsub?

-Taylor

> On Mar 29, 2016, at 5:36 PM, Billie Rinaldi <bi...@apache.org> wrote:
> 
>> On Tue, Mar 29, 2016 at 12:46 PM, Casey Stella <ce...@gmail.com> wrote:
>> 
>> Regarding the use of effective_tld_names.dat, it is in use currently in the
>> Whois enrichment adapter (for stripping top level domains from domains),
>> but that adapter is not turned on in the tech preview.  That being said,
>> it's likely we will want to use that file in the future.  Since this is a
>> reference file and the reason for the binary-only exclusion is "By
>> including only the object/binary form, there is less exposed surface area
>> of the third-party work from which a work might be derived; this addresses
>> the second guiding principle of this policy.", it would seem that its
>> inclusion as a piece of reference data lessens the exposed surface area
>> from which a work might be derived, no?
>> 
> 
> I read that part as saying that it's only okay to include the binary
> version; but since this is textual data there is no binary version of these
> files that we could include.  However, I missed this part on my first read:
> "For small amounts of source that is directly consumed by the ASF product
> at runtime in source form, and for which that source is unmodified and
> unlikely to be changed anyway (say, by virtue of being specified by a
> standard), inclusion of appropriately labeled source is also permitted. An
> example of this is the web-facesconfig_1_0.dtd, whose inclusion is mandated
> by the JSR 127: JavaServer Faces specification."
> 
> So it sounds like we could argue that these 3 files (which are all
> identical) are a small amount of source, and we will be allowed to include
> them with an appropriate reference in our LICENSE **as long as we never
> modify the effective_tld_names.dat files**.
> 
> 
>> 
>> Casey
>> 
>>> On Tue, Mar 29, 2016 at 2:55 PM, Billie Rinaldi <bi...@apache.org> wrote:
>>> 
>>> These files have Mozilla Public License, which has an unusual policy that
>>> says we should only include them in binary form (!) -- see
>>> http://www.apache.org/legal/resolved.html#category-b.  Can we get rid of
>>> them?
>>> metron-streaming/Metron-Common/src/test/resources/effective_tld_names.dat
>>> 
>>> 
>> metron-streaming/Metron-MessageParsers/src/test/resources/effective_tld_names.dat
>>> 
>>> 
>> metron-streaming/Metron-Topologies/src/main/resources/effective_tld_names.dat
>>> 
>>> The files at metron-ui/lib/public/font/* seem to have SIL Open Font
>> License
>>> (https://github.com/FortAwesome/Font-Awesome#license), which has the
>> same
>>> restriction, but they're okay since they're binary.  We need to add their
>>> info to our LICENSE.
>>> 
>>> - checksums and signature are valid -- next time include a md5 signature
>>> - DISCLAIMER is correct -- file name should include "incubating" but
>>> "incubator" is close
>>> - no binaries in source tarball
>>> - build is successful
>>> 
>>> Billie
>>> 
>>> On Tue, Mar 22, 2016 at 3:56 PM, James Sirota <js...@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
>>>> 
>>>> 
>>> 
>>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by Billie Rinaldi <bi...@apache.org>.

On Tue, Mar 29, 2016 at 12:46 PM, Casey Stella <ce...@gmail.com> wrote:

> Regarding the use of effective_tld_names.dat, it is in use currently in the
> Whois enrichment adapter (for stripping top level domains from domains),
> but that adapter is not turned on in the tech preview.  That being said,
> it's likely we will want to use that file in the future.  Since this is a
> reference file and the reason for the binary-only exclusion is "By
> including only the object/binary form, there is less exposed surface area
> of the third-party work from which a work might be derived; this addresses
> the second guiding principle of this policy.", it would seem that its
> inclusion as a piece of reference data lessens the exposed surface area
> from which a work might be derived, no?
>

I read that part as saying that it's only okay to include the binary
version; but since this is textual data there is no binary version of these
files that we could include.  However, I missed this part on my first read:
"For small amounts of source that is directly consumed by the ASF product
at runtime in source form, and for which that source is unmodified and
unlikely to be changed anyway (say, by virtue of being specified by a
standard), inclusion of appropriately labeled source is also permitted. An
example of this is the web-facesconfig_1_0.dtd, whose inclusion is mandated
by the JSR 127: JavaServer Faces specification."

So it sounds like we could argue that these 3 files (which are all
identical) are a small amount of source, and we will be allowed to include
them with an appropriate reference in our LICENSE **as long as we never
modify the effective_tld_names.dat files**.


>
> Casey
>
> On Tue, Mar 29, 2016 at 2:55 PM, Billie Rinaldi <bi...@apache.org> wrote:
>
> > These files have Mozilla Public License, which has an unusual policy that
> > says we should only include them in binary form (!) -- see
> > http://www.apache.org/legal/resolved.html#category-b.  Can we get rid of
> > them?
> > metron-streaming/Metron-Common/src/test/resources/effective_tld_names.dat
> >
> >
> metron-streaming/Metron-MessageParsers/src/test/resources/effective_tld_names.dat
> >
> >
> metron-streaming/Metron-Topologies/src/main/resources/effective_tld_names.dat
> >
> > The files at metron-ui/lib/public/font/* seem to have SIL Open Font
> License
> > (https://github.com/FortAwesome/Font-Awesome#license), which has the
> same
> > restriction, but they're okay since they're binary.  We need to add their
> > info to our LICENSE.
> >
> > - checksums and signature are valid -- next time include a md5 signature
> > - DISCLAIMER is correct -- file name should include "incubating" but
> > "incubator" is close
> > - no binaries in source tarball
> > - build is successful
> >
> > Billie
> >
> > On Tue, Mar 22, 2016 at 3:56 PM, James Sirota <js...@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
> > >
> > >
> >
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by "P. Taylor Goetz" <pt...@gmail.com>.

Those .dat files are under the Mozilla Public License v. 2.0.

So to comply you can point to the files (the way I pointed out earlier in the thread) in the LICENSE file and add the following text:

This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at https://mozilla.org/MPL/2.0/.

See Appendix A here [1], and the Legal Discuss JIRA here [2]. The MPL [1] explicitly states that putting the notice the LICENSE file is okay.

-Taylor

[1] https://www.mozilla.org/en-US/MPL/2.0/ <https://www.mozilla.org/en-US/MPL/2.0/>
[2] https://issues.apache.org/jira/browse/LEGAL-77

> On Mar 29, 2016, at 3:46 PM, Casey Stella <ce...@gmail.com> wrote:
> 
> Regarding the use of effective_tld_names.dat, it is in use currently in the
> Whois enrichment adapter (for stripping top level domains from domains),
> but that adapter is not turned on in the tech preview.  That being said,
> it's likely we will want to use that file in the future.  Since this is a
> reference file and the reason for the binary-only exclusion is "By
> including only the object/binary form, there is less exposed surface area
> of the third-party work from which a work might be derived; this addresses
> the second guiding principle of this policy.", it would seem that its
> inclusion as a piece of reference data lessens the exposed surface area
> from which a work might be derived, no?
> 
> Casey
> 
> On Tue, Mar 29, 2016 at 2:55 PM, Billie Rinaldi <bi...@apache.org> wrote:
> 
>> These files have Mozilla Public License, which has an unusual policy that
>> says we should only include them in binary form (!) -- see
>> http://www.apache.org/legal/resolved.html#category-b.  Can we get rid of
>> them?
>> metron-streaming/Metron-Common/src/test/resources/effective_tld_names.dat
>> 
>> metron-streaming/Metron-MessageParsers/src/test/resources/effective_tld_names.dat
>> 
>> metron-streaming/Metron-Topologies/src/main/resources/effective_tld_names.dat
>> 
>> The files at metron-ui/lib/public/font/* seem to have SIL Open Font License
>> (https://github.com/FortAwesome/Font-Awesome#license), which has the same
>> restriction, but they're okay since they're binary.  We need to add their
>> info to our LICENSE.
>> 
>> - checksums and signature are valid -- next time include a md5 signature
>> - DISCLAIMER is correct -- file name should include "incubating" but
>> "incubator" is close
>> - no binaries in source tarball
>> - build is successful
>> 
>> Billie
>> 
>> On Tue, Mar 22, 2016 at 3:56 PM, James Sirota <js...@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
>>> 
>>> 
>>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by Casey Stella <ce...@gmail.com>.

Regarding the use of effective_tld_names.dat, it is in use currently in the
Whois enrichment adapter (for stripping top level domains from domains),
but that adapter is not turned on in the tech preview.  That being said,
it's likely we will want to use that file in the future.  Since this is a
reference file and the reason for the binary-only exclusion is "By
including only the object/binary form, there is less exposed surface area
of the third-party work from which a work might be derived; this addresses
the second guiding principle of this policy.", it would seem that its
inclusion as a piece of reference data lessens the exposed surface area
from which a work might be derived, no?

Casey

On Tue, Mar 29, 2016 at 2:55 PM, Billie Rinaldi <bi...@apache.org> wrote:

> These files have Mozilla Public License, which has an unusual policy that
> says we should only include them in binary form (!) -- see
> http://www.apache.org/legal/resolved.html#category-b.  Can we get rid of
> them?
> metron-streaming/Metron-Common/src/test/resources/effective_tld_names.dat
>
> metron-streaming/Metron-MessageParsers/src/test/resources/effective_tld_names.dat
>
> metron-streaming/Metron-Topologies/src/main/resources/effective_tld_names.dat
>
> The files at metron-ui/lib/public/font/* seem to have SIL Open Font License
> (https://github.com/FortAwesome/Font-Awesome#license), which has the same
> restriction, but they're okay since they're binary.  We need to add their
> info to our LICENSE.
>
> - checksums and signature are valid -- next time include a md5 signature
> - DISCLAIMER is correct -- file name should include "incubating" but
> "incubator" is close
> - no binaries in source tarball
> - build is successful
>
> Billie
>
> On Tue, Mar 22, 2016 at 3:56 PM, James Sirota <js...@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
> >
> >
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by Billie Rinaldi <bi...@apache.org>.

These files have Mozilla Public License, which has an unusual policy that
says we should only include them in binary form (!) -- see
http://www.apache.org/legal/resolved.html#category-b.  Can we get rid of
them?
metron-streaming/Metron-Common/src/test/resources/effective_tld_names.dat
metron-streaming/Metron-MessageParsers/src/test/resources/effective_tld_names.dat
metron-streaming/Metron-Topologies/src/main/resources/effective_tld_names.dat

The files at metron-ui/lib/public/font/* seem to have SIL Open Font License
(https://github.com/FortAwesome/Font-Awesome#license), which has the same
restriction, but they're okay since they're binary.  We need to add their
info to our LICENSE.

- checksums and signature are valid -- next time include a md5 signature
- DISCLAIMER is correct -- file name should include "incubating" but
"incubator" is close
- no binaries in source tarball
- build is successful

Billie

On Tue, Mar 22, 2016 at 3:56 PM, James Sirota <js...@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
>
>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by George Vetticaden <gv...@hortonworks.com>.

+ 1 (binding) to release
I have verified the following:

1. Was able to build metron successfully
2. Successfully deployed Single Node Vagrant Setup
2. Successfully deployed 10 Node Install of Metron using AWS Ansible
Playbook


-- 
George VetticadenPrincipal, COE
gvetticaden@hortonworks.com
(630) 909-9138





On 3/23/16, 11:27 AM, "James Sirota" <js...@hortonworks.com> wrote:

>Small correction on the validation instructions.  For Step 1, execute the
>mvn command from incubator-metron/ and not
>incubator-metron/metron-streaming/
>
>Thanks,
>James 
>
>
>
>
>On 3/22/16, 3:56 PM, "James Sirota" <js...@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_rc
>>5
>>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
>>

Re: [VOTE] Release of Metron_0.1BETA_rc5

Posted by James Sirota <js...@hortonworks.com>.

Small correction on the validation instructions.  For Step 1, execute the mvn command from incubator-metron/ and not incubator-metron/metron-streaming/

Thanks,
James 




On 3/22/16, 3:56 PM, "James Sirota" <js...@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
>