Status: To Do
Affects Version/s: 0.4.3
Fix Version/s: Next + 1
Environment:i) AWS Image: Centos6 - AWS t2.t2xlarge [32 GB Memory, 8 Cores, 64 bit] based on metron-deployment/development/centos6/
ii) AWS Single Node Cluster Deployment Using Vagrant: MacOS
iii) AMI "GCR-Xetron Demo"/"ami-93cb4ff7" - AWS t2.t2xlarge
The pull request has two potential solutions for deploying to Metron to AWS.
i) AWS Single Node Cluster Deployment Using Vagrant
ii) AWS Single Node Cluster Deployment Using an AMI
i) AWS Single Node Cluster Deployment Using Vagrant:
I was able to deploy Metron as a single node to AWS using Vagrant on MacOS.
It was tested using the latest Metron code (as of 2018-01-30 - 8:00am UTC) that was in git. I'm assuming the latest that was in git is 0.4.3 that is progress.
ii) AWS Single Node Cluster Deployment Using an AMI:
In addition to including instructions for deploying 0.4.3 using Vagrant on a Mac I also included instructions for deploying to AWS using a preexisting AMI (I made the following AMI public as a proof-of-concept: "GCR-Xetron Demo"/"ami-93cb4ff7"). This might be the quicket option for deployment since no preinstall requirments would be needed.
***PULL REQUEST CHECKLIST ITEMS***
"For documentation related changes:"
Running cd site-book, mvn site produced "BUILD SUCCESS"
"For code changes:"
Was not sure where to run "mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh ". Core Metron Code was not changed. For i) the following code were newly added/modified:
[Vagrant to work with aws]
[changing eth1 to eth0]
"How the change may be verified: "
You should be able to see Ambari after following instructions (http://<elasticip>:8080)