nickwallen opened a new pull request #1565: METRON-2321 Remove Legacy AWS Deployment Path URL: https://github.com/apache/metron/pull/1565 The automated AWS deployment mechanism (`metron-deployment/amazon-ec2`) should be removed. It is no longer the preferred installation path for deploying to AWS. There are many problems with maintaining this deployment method. * It deploys an insecure cluster by default. * It produces a cluster that does not survive a reboot. * It is difficult for the the community to support a code path that is not free. * This is no longer the preferred installation path for AWS. * It is difficult for the community to support a code path that is not free. * Is a point-of-confusion for new Metron users. If a user wants to deploy to AWS, they should launch their EC2 nodes, install Ambari, and then using the MPack to deploy Metron. That is the preferred installation path for AWS. This has been discussed on the mailing list. * https://lists.apache.org/thread.html/4ba83a634a10ecc9380d4592a6fe568dfaf6a1b5da433cc84b129e6a@%3Cdev.metron.apache.org%3E ## Acceptance Testing This PR can be tested using the centos6 development environment. Ensure that we can continue to parse, enrich, and index telemetry. Verify data is flowing through the system, from parsing to indexing 1. Build the site-book and review its output. ``` cd site-book mvn clean site open target/site/index.html ``` 1. Start up the centos6 dev environment. ``` cd metron-deployment/development/centos6 vagrant destroy -f vagrant up ``` 1. Open Ambari and navigate to the Metron service http://node1:8080/#/main/services/METRON/summary 1. Open the Alerts UI. Verify alerts show up in the main UI - click the search icon (you may need to wait a moment for them to appear) 1. Go to the Alerts UI and ensure that an ever increasing number of telemetry from Bro, Snort, and YAF are visible by watching the total alert count increase over time. 1. Ensure that geoip enrichment is occurring. The telemetry should contain fields like `enrichments:geo:ip_src_addr:location_point`. 1. Head back to Ambari and select the Kibana service http://node1:8080/#/main/services/KIBANA/summary 1. Open the Kibana dashboard via the "Metron UI" option in the quick links 1. Verify the dashboard is populating ## Pull Request Checklist ### For all changes: - [ ] 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). - [ ] Does your PR title start with METRON-XXXX where XXXX 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 documentation related changes: - [ ] 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`: - [ ] Have you ensured that any documentation diagrams have been updated, along with their source files, using [draw.io](https://www.draw.io/)? See [Metron Development Guidelines](https://cwiki.apache.org/confluence/display/METRON/Development+Guidelines) for instructions.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
