[GitHub] metron issue #916: METRON-1434 - Ability to deploy Metron full dev as a sing...
Github user as22323 commented on the issue: https://github.com/apache/metron/pull/916 Thanks. If needed here is the deployment script that worked with Metron 0.4.1. https://github.com/LTW-GCR-CSOC/csoc-installation-scripts/blob/master/amazon-deploy/Metron/aws-vagrant_0.4.1/Vagrantfile ---
[GitHub] metron pull request #916: METRON-1434 - Ability to deploy Metron full dev as...
GitHub user as22323 opened a pull request: https://github.com/apache/metron/pull/916 METRON-1434 - Ability to deploy Metron full dev as a single node (centos6) to AWS with Vagran and AMI ## Contributor Comments [Please place any comments here. A description of the problem/enhancement, how to reproduce the issue, your testing methodology, etc.] ## Pull Request Checklist Thank you for submitting a contribution to Apache Metron. Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions. Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) for complete smoke testing guides. In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel). - [x] Does your PR title start with METRON- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically master)? ### For code changes: - [x] Have you included steps to reproduce the behavior or problem that is being changed or addressed? - [x] Have you included steps or a guide to how the change may be verified and tested manually? - [ ] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via: ``` mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh ``` - [ ] Have you written or updated unit tests and or integration tests to verify your changes? - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent? ### For documentation related changes: - [x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via `site-book/target/site/index.html`: ``` cd site-book mvn site ``` Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request. You can merge this pull request into a Git repository by running: $ git pull https://github.com/as22323/metron master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/metron/pull/916.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 #916 commit 54f44ac9c9cb36fb5054c80e8f796fb5b2873fe1 Author: as22323 <a.k.shah@...> Date: 2018-01-30T04:49:36Z added section for aws-centos6 commit e95d73c8e94ff450aa9fa28af4db8ebce6c9c6ff Author: as22323 <a.k.shah@...> Date: 2018-01-30T04:52:10Z Update README.md commit bb91158a60edefd4263db598a109ee151d3a6cc1 Author: as22323 <a.k.shah@...> Date: 2018-01-30T04:52:21Z Update README.md commit f794c87c24e2dbdc24999bc25e0d35d7f553c6d8 Author: as22323 <a.k.shah@...> Date: 2018-01-30T04:53:15Z Update README.md commit dd149768690174d74d274832b1e99d4e56810072 Author: as22323 <a.k.shah@...> Date: 2018-01-30T04:53:26Z Update README.md commit 977969966f4f7e7d8e71713b3819c9a378a99cb6 Author: as22323 <a.k.shah@...> Date: 2018-01-30T04:54:22Z Update README.md commit ab403dd9c21e4a6b2fadddf393f2318e17cd7dd9 Author: as22323 <a.k.shah@...> Date: 2018-01-30T04:56:15Z Update README.md commit ce345e9b88b7e1376b328770701f5ced73a147a0 Author: as22323 <a.k.shah@...> Date: 2018-01-30T04:56:32Z Update README.md commit a69c231d895ba40590316f71553acddada050293 Author: as22323 <a.k.shah@...> Date: 2018-01-30T05:00:53Z Update README.md commit 6cf22e6e61735dcd99b9940d319a2811ac758e63 Author: as22323 <a.k.shah@...> Date: 2018-01-30T05:04:21Z Update README.md commit 8a150df08440fa39678ba8826ce14afdd456552d Author
[GitHub] metron issue #754: METRON-1184 EC2 Deployment - Updating control_path to acc...
Github user as22323 commented on the issue: https://github.com/apache/metron/pull/754 Just an FYI: This PR is to simply change "control_path = ~/.ssh/ansible-ssh-%%C"(in ../amazon-ec2/ansible.cfg) to "control_path = ~/.ssh/ansbile-ssh-%%h-%%r" to allow linux systems to deploy to EC2. When I tested the change with Mac it didn't throw any errors at the same point for ""TASK [setup] ***" ---
[GitHub] metron issue #754: METRON-1184 EC2 Deployment - Updating control_path to acc...
Github user as22323 commented on the issue: https://github.com/apache/metron/pull/754 Hello, Just wondering if what needs to be done next to get this committed. ---
[GitHub] metron pull request #754: METRON-1184 EC2 Deployment - Updating control_path...
GitHub user as22323 opened a pull request:
https://github.com/apache/metron/pull/754
METRON-1184 EC2 Deployment - Updating control_path to accommodate for Linux
## Contributor Comments - EC2 Deployment - Updating control_path to
accommodate for Linux
In Metron 0.4.1-rc4, using "control_path =
~/.ssh/ansible-ssh-%%C"(amazon-ec2/ansible.cfg) in a Linux environment ( such
as ClearOS release 7.4.0[ClearOS is based on CentOS] with npm 3.10.10, node
6.11.1, docker 1.12.6, mvn 3.3.9, ansible 2.2.2.0, No Vagrant) could throw the
following error:
```
"TASK [setup]
***
fatal: [ec2-xx-yy-0-130.us-west-2.compute.amazonaws.com]: UNREACHABLE! =>
{"changed": false, "msg": "Failed to connect to the host via ssh:
percent_expand: unknown key %C\r\n", "unreachable": true}"
```
I noticed the line was formally "control_path = %(directory)s/%%h-%%p-%%r"
(which worked for the Linux env above)] was changed to "control_path =
~/.ssh/ansible-ssh-%%C"
This PR is to change the line to "control_path =
~/.ssh/ansbile-ssh-%%h-%%r" to make amazon-ec2 also potentially deployable with
Linux while preserving a small path length.
This is an attempt to resolve the path length issue as described in the
following links:
http://docs.ansible.com/ansible/latest/intro_configuration.html - see
control_path
https://github.com/ansible/ansible/issues/11536#issuecomment-153030743 -
using %%C
---
Testing method:
Made change to ansible.cfg file (in Metron 0.4.1-rc4) as described in this
PR then ran ./run.sh (metron/metron-deployment/amazon-ec2/).
If successful then the following should appear:
```
ok: [x.compute.amazonaws.com] => {
"Success": [
"Apache Metron deployed successfully",
" Metron @ http://x.compute.amazonaws.com:5000;,
" Ambari @ http://x.compute.amazonaws.com:8080;,
" Sensor Status @ http://x.compute.amazonaws.com:2812;,
" Zookeeper @ x.compute.amazonaws.com:2181",
" Kafka @
x.compute.amazonaws.com:6667,x..compute.amazonaws.com:6667,x.compute.amazonaws.com:6667,x.compute.amazonaws.com:6667,x.compute.amazonaws.com:6667",
"For additional information, see https://metron.apache.org/'"
]
}
PLAY RECAP
*
x..compute.amazonaws.com : ok=44 changed=28 unreachable=0
failed=0
x..compute.amazonaws.com : ok=44 changed=28 unreachable=0
failed=0
x..compute.amazonaws.com : ok=44 changed=28 unreachable=0
failed=0
x..compute.amazonaws.com : ok=44 changed=28 unreachable=0
failed=0
x..compute.amazonaws.com : ok=204 changed=112 unreachable=0
failed=0
x..compute.amazonaws.com : ok=50 changed=32 unreachable=0
failed=0
x..compute.amazonaws.com : ok=44 changed=28 unreachable=0
failed=0
x..compute.amazonaws.com : ok=79 changed=26 unreachable=0
failed=0
x..compute.amazonaws.com : ok=44 changed=28 unreachable=0
failed=0
x..compute.amazonaws.com : ok=44 changed=28 unreachable=0
failed=0
localhost : ok=20 changed=16 unreachable=0failed=0
```
## Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our [Development
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
for the complete guide to follow for contributions.
Please refer also to our [Build Verification
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow
these guidelines and ask you to double check the following:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? If not one needs to
be created at [Metron
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
https://issues.apache.org/jira/browse/METRON-1184
- [x] Does your PR title start with METRON- where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
### For code changes:
[GitHub] metron issue #713: METRON-1130 - Updating Amazon EC2 README.md
Github user as22323 commented on the issue: https://github.com/apache/metron/pull/713 Thanks. I have updated to "master". According to the Metron Dev Guidelines I am suppose to assign the METRON JIRA ticket to my self. I'm not sure how to do that. --- 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] metron pull request #713: METRON-1130 - Updating Amazon EC2 README.md
GitHub user as22323 opened a pull request: https://github.com/apache/metron/pull/713 METRON-1130 - Updating Amazon EC2 README.md ## Contributor Comments Hello, This is my first time submitting a pull request to the Apache Metron project. Feel free to point me in the right direction if I am not doing this right. The suggested updates were based on my experience of using ClearOS 7.4.0 (Distro is based on CentOS) as a host to install Apache Metron 0.4.0 in Amazon EC2. FYI: Here is a list of versions that seemed break/cause issues when installing: -Ansible 2.0.0.2 -Maven 3.0.5 ## Pull Request Checklist Thank you for submitting a contribution to Apache Metron. Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions. Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) for complete smoke testing guides. In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel). - [x] Does your PR title start with METRON- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)? ### For code changes: - [ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed? - [ ] Have you included steps or a guide to how the change may be verified and tested manually? - [ ] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via: ``` mvn -q clean integration-test install && build_utils/verify_licenses.sh ``` - [ ] Have you written or updated unit tests and or integration tests to verify your changes? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent? ### For documentation related changes: - [x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via `site-book/target/site/index.html`: ``` cd site-book mvn site ``` Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request. You can merge this pull request into a Git repository by running: $ git pull https://github.com/as22323/metron master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/metron/pull/713.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 #713 commit 095be23dce0f818a98a1fc587053d133ca542856 Author: JonZeolla <zeo...@gmail.com> Date: 2017-06-28T18:04:39Z METRON-999 Add virtualization support checks to platform-info.sh (JonZeolla via jonzeolla) closes apache/metron#618 commit df94ed40523db375b0bac4601a7efffa5a1fede5 Author: justinleet <justinjl...@gmail.com> Date: 2017-06-30T13:21:17Z METRON-1004 Travis CI - Job Exceeded Maximum Time Limit (justinleet) closes apache/metron#624 commit a5b13777a92418155da61864e98fc24cde866501 Author: mattf-horton <mfo...@hortonworks.com> Date: 2017-07-02T22:38:14Z METRON-877 Extract core implementation and UDF support, create metron-stellar module (mattf-horton) closes apache/metron#616 commit ab87bdf673e151da4b6352da6b0f4a6957f4777b Author: ottobackwards <ottobackwa...@gmail.com> Date: 2017-07-04T11:47:43Z METRON-1007 Ship the metron-management jar as part of the mpack install (ottobackwards) closes apache/metron#627 commit cc7bbc94870f0e0d5026c14ac710ca8882d0589b Author: JonZeolla <zeo...@gmail.com> Date: 2017-07-05T01:52:00Z METRON-508 Expand Elasticsearch templates to support the standard bro lo
