GitHub user nickwallen opened a pull request:
https://github.com/apache/incubator-metron/pull/45
METRON-67 YAF Probe Not Landing Data in Kafka
- METRON-67 YAF Probe Not Landing Data in Kafka
- METRON-68 Create Post-Provisioning Report
```
TASK [debug]
*******************************************************************
ok: [localhost] => {
"Success": [
"Apache Metron deployed successfully",
" Metron @
http://ec2-52-37-255-142.us-west-2.compute.amazonaws.com:5000";,
" Ambari @
http://ec2-52-37-225-202.us-west-2.compute.amazonaws.com:8080";,
" Sensors @ ec2-52-37-225-202.us-west-2.compute.amazonaws.com on
tap0",
"For additional information, see
https://metron.incubator.apache.org/'"
]
}
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickwallen/incubator-metron METRON-67
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/45.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 #45
----
commit 7e37f4ae9fe5d41203b6b028501c8a9ea946b72b
Author: Nick Allen <[email protected]>
Date: 2016-03-14T17:27:39Z
METRON-68 Added instructions for dealing with AWS EC2 environment
commit 29b68340c6ef392a6d8c201d6262a4b0fc3b0cf1
Author: Nick Allen <[email protected]>
Date: 2016-03-14T21:30:19Z
METRON-67 YAF was not being started successfully after deployment
commit 4b59b626e1601371386875ee1569eabeefc7b388
Author: Nick Allen <[email protected]>
Date: 2016-03-14T21:31:07Z
METRON-68 Added provisioning report
Refactored bro deployment scripts to match the pattern of others
Added URL to Ambari to the message displayed to the user
Removed unnecessary whitespace
Ignore errors from data load to achieve some level of idempotency
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
