[GitHub] incubator-metron pull request: Deployment

2016-01-26 Thread merrimanr 
Github user merrimanr closed the pull request at:

https://github.com/apache/incubator-metron/pull/14


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron pull request: METRON-21

2016-01-26 Thread merrimanr 
GitHub user merrimanr opened a pull request:

https://github.com/apache/incubator-metron/pull/15

METRON-21

This pull request contains the Ansible deployment scripts. Currently the 
scripts support 2 deployment types: deploying Metron to a single node VM (full 
install including Ambari and cluster) for development and testing purposes and 
deploying Metron to a cluster that already exists. The Pcap source works end to 
end and other sources will be added in future iterations.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/merrimanr/incubator-metron master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-metron/pull/15.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15


commit bafa055802cfb3bbb19d74fdcac669bdd48dac6e
Author: rmerriman 
Date:   2016-01-22T22:18:02Z

Added ability to configure a topic for each source

commit dc7f8a8b6ef59108ac7c5004875f7c51e48f3164
Author: rmerriman 
Date:   2016-01-22T23:47:39Z

Ansible and vagrant scripts to deploy Metron

commit b1a772313c36c4c8fb254db9a6914b47c2d081bb
Author: rmerriman 
Date:   2016-01-25T16:32:20Z

Revert "Added ability to configure a topic for each source"

This reverts commit bafa055802cfb3bbb19d74fdcac669bdd48dac6e.

commit dd5b60bbc12f23e95c38557a915a0f73b00f47d4
Author: Nick Allen 
Date:   2016-01-25T19:35:10Z

Using an older forked version of Bro that has a Kafka writer to publish Bro 
data

commit cacb1cf85e945d65f729c8ddaf05ba1ae86a3731
Author: rmerriman 
Date:   2016-01-25T20:12:39Z

Moved hadoop setup tasks to separate role and updated documentation

commit 4da5cc4eb9ce60eb752b7c26225b32d819aae901
Author: rmerriman 
Date:   2016-01-25T20:54:03Z

Removed redundant HBase create

commit f829f3edc5efccb8a2bc7e6418133cf3cd84ccd9
Author: Nick Allen 
Date:   2016-01-25T20:54:09Z

Using yum instead of rpm which handles idempotency stuffs

commit 99b40d627e3c721d4a42787338cef4d8d73da508
Author: Nick Allen 
Date:   2016-01-26T15:04:44Z

Merged with master

commit aba9e9c55db91ee1d0b8e84095578d17d572591e
Author: rmerriman 
Date:   2016-01-22T23:47:39Z

Ansible and vagrant scripts to deploy Metron

commit 268ffda035b66de3965f16a8949a8c9a9f81526f
Author: Nick Allen 
Date:   2016-01-25T19:35:10Z

Using an older forked version of Bro that has a Kafka writer to publish Bro 
data

commit d8ef56e8b01373c1372e94ae5076a8f8d30469df
Author: Nick Allen 
Date:   2016-01-25T20:54:09Z

Using yum instead of rpm which handles idempotency stuffs

commit ab77fc2917949abb7a4a19f8dbb8f0da4f616d82
Author: rmerriman 
Date:   2016-01-25T20:12:39Z

Moved hadoop setup tasks to separate role and updated documentation

commit 0a52ed53438753e6d73b75a996c5a57327be3f0c
Author: rmerriman 
Date:   2016-01-25T20:54:03Z

Removed redundant HBase create

commit 2d7637a907ad44608819082d26dbe20d758fceb0
Author: Nick Allen 
Date:   2016-01-26T16:03:21Z

missing var 'pcap_hbase_table' but no mo, fo sho

commit f3365f112aa42c6fce7c1419c3b01914c0704a5b
Author: Nick Allen 
Date:   2016-01-26T16:13:53Z

Turning on ansible pipelining to speed up deployments

commit c8da475df25201708d179f00a5e347a9558bcfbf
Author: rmerriman 
Date:   2016-01-26T16:20:51Z

.gitignore additions

commit 6075661ff71e89847f448a09351cce010275c53c
Author: Nick Allen 
Date:   2016-01-26T16:59:24Z

Remove tab characters which are treated as literal characters, not 
whitespace.  Different behavior in Ansible 2+

commit d73d38ae2dbdbff216ff00628225b808c38456a3
Author: rmerriman 
Date:   2016-01-26T17:04:20Z

Merge branch 'master' of github.com:merrimanr/incubator-metron

Conflicts:
deployment/.gitignore
deployment/inventory/metron_example/group_vars/all
deployment/inventory/singlenode-vagrant/group_vars/all
deployment/roles/bro/tasks/main.yml
deployment/vagrant/multinode-vagrant/ansible.cfg
deployment/vagrant/singlenode-vagrant/ansible.cfg

commit ac91bc27f781699cd3e91859369b47ef0a40f732
Author: Nick Allen 
Date:   2016-01-26T17:16:08Z

Was missing zlib-devel as a Snort dependency

commit 260fc7b7a3f5278030e816f9a24d1afffeeb3f42
Author: rmerriman 
Date:   2016-01-26T17:20:25Z

Merge branch 'master' of github.com:merrimanr/incubator-metron




---
If your project is set up for it,

Re: [GitHub] incubator-metron pull request: Deployment

2016-01-26 Thread Ryan Merriman 
Here is the new pull request with the modifications:

https://github.com/apache/incubator-metron/pull/15


This only includes the additions our team contributed since METRON-2.

On 1/26/16, 8:39 AM, "Ryan Merriman"  wrote:

>Mark,
>
>We went back and merged METRON-2 into the master branch so your pull
>request is in the commit history now.  Let me know if something doesn’t
>look right.  I am going to add the most recent deployment changes on top
>of that and submit a new pull request.  We would love your feedback since
>you are experienced with Ansible.
>
>
>Sorry for the misunderstanding.  Some of us are new to this process and
>the fact that your pull request didn’t get merged before the big refactor
>tripped us up.
>
>Ryan Merriman
>
>On 1/25/16, 8:54 PM, "Ryan Merriman"  wrote:
>
>>Really sorry about that Mark.  I was so focused on getting everything
>>working that I wasn¹t thinking about the commit history.  I will get that
>>fixed.  I promise it wasn¹t intentional.
>>
>>On 1/25/16, 8:27 PM, "Mark Bittmann"  wrote:
>>
>>>Ryan,
>>>
>>>It looks like you took all the code from PR #3 resubmitted it as your
>>>own
>>>in PR #14. Obviously you put in a ton of extra work on top of it, and
>>>I'm
>>>excited to see you build off of it, but I would be personally
>>>disappointed to not get any credit for laying the foundation for all of
>>>the Hadoop components.
>>>
>>>https://github.com/apache/incubator-metron/pull/3
>>>
>>>I would think it would be better for the community to have multiple
>>>people contributing incrementally. Wouldn't it make more sense to pull
>>>in
>>>PR #3 rather than copying the code into a new PR and losing the history?
>>>
>>>Mark
>>>
>>>
>>>
>>>
>>>
>>>
>>>On 1/25/16, 8:38 PM, "merrimanr"  wrote:
>>>
Github user merrimanr commented on the pull request:


https://github.com/apache/incubator-metron/pull/14#issuecomment-1747614
3
3
  
https://issues.apache.org/jira/browse/METRON-21


---
If your project is set up for it, you can reply to this email and have
your
reply appear on GitHub as well. If your project does not have this
feature
enabled and wishes so, or if the feature is enabled but not working,
please
contact infrastructure at infrastruct...@apache.org or file a JIRA
ticket
with INFRA.
---
>>
>>
>

Re: [GitHub] incubator-metron pull request: Deployment

2016-01-26 Thread Mark Bittmann 
Thanks a lot Ryan for refactoring to include the original pull request. I 
really appreciate you taking the time to do that. I will carve out some time 
this week to go through the new code and test it. 




On 1/26/16, 1:32 PM, "Ryan Merriman"  wrote:

>Here is the new pull request with the modifications:
>
>https://github.com/apache/incubator-metron/pull/15
>
>
>This only includes the additions our team contributed since METRON-2.
>
>On 1/26/16, 8:39 AM, "Ryan Merriman"  wrote:
>
>>Mark,
>>
>>We went back and merged METRON-2 into the master branch so your pull
>>request is in the commit history now.  Let me know if something doesn’t
>>look right.  I am going to add the most recent deployment changes on top
>>of that and submit a new pull request.  We would love your feedback since
>>you are experienced with Ansible.
>>
>>
>>Sorry for the misunderstanding.  Some of us are new to this process and
>>the fact that your pull request didn’t get merged before the big refactor
>>tripped us up.
>>
>>Ryan Merriman
>>
>>On 1/25/16, 8:54 PM, "Ryan Merriman"  wrote:
>>
>>>Really sorry about that Mark.  I was so focused on getting everything
>>>working that I wasn¹t thinking about the commit history.  I will get that
>>>fixed.  I promise it wasn¹t intentional.
>>>
>>>On 1/25/16, 8:27 PM, "Mark Bittmann"  wrote:
>>>
Ryan,

It looks like you took all the code from PR #3 resubmitted it as your
own
in PR #14. Obviously you put in a ton of extra work on top of it, and
I'm
excited to see you build off of it, but I would be personally
disappointed to not get any credit for laying the foundation for all of
the Hadoop components.

https://github.com/apache/incubator-metron/pull/3

I would think it would be better for the community to have multiple
people contributing incrementally. Wouldn't it make more sense to pull
in
PR #3 rather than copying the code into a new PR and losing the history?

Mark






On 1/25/16, 8:38 PM, "merrimanr"  wrote:

>Github user merrimanr commented on the pull request:
>
>
>https://github.com/apache/incubator-metron/pull/14#issuecomment-1747614
>3
>3
>  
>https://issues.apache.org/jira/browse/METRON-21
>
>
>---
>If your project is set up for it, you can reply to this email and have
>your
>reply appear on GitHub as well. If your project does not have this
>feature
>enabled and wishes so, or if the feature is enabled but not working,
>please
>contact infrastructure at infrastruct...@apache.org or file a JIRA
>ticket
>with INFRA.
>---
>>>
>>>
>>
>