[
https://issues.apache.org/jira/browse/METRON-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427966#comment-16427966
]
ASF GitHub Bot commented on METRON-1434:
----------------------------------------
Github user as22323 commented on the issue:
https://github.com/apache/metron/pull/916
Hello, Just wondering what the the /contrib is folder for? If the files in
/contrib is not part of the core maintenance(continuous update for n+1) then
perhaps we can make a reference to the Vagrant/AWS deployment method in this
doc [metron-deployment/other-examples/README.md](PR 980) then store the code
and the "notice that sets expectation" in the /contrib folder. Right now PR 980
points to the Vagrantfile at our github site (as apposed to putting it into
/contrib folder within the Apache Metron project).
The proposed update could look like this (see file path structure):
The README.md here will list the Vagrant/AWS method.
https://github.com/LTW-GCR-CSOC/metron/tree/master/metron-deployment/other-examples
The readme.md in this path can refer to the "notice" and Vagrantfile in the
/contrib folder:
https://github.com/LTW-GCR-CSOC/metron/tree/master/metron-contrib/Metron-041SingleNodeEC2Vagrant/README.md
https://github.com/LTW-GCR-CSOC/metron/tree/master/metron-contrib/Metron-041SingleNodeEC2Vagrant/Vagrantfile
FYI I'm working on using Vagrant to deploy to 0.4.1 to ESXi. That could be
posted at some point using the file structure above.
> Ability to deploy Metron full dev as a single node (centos6) to AWS with
> vagrant and AMI
> ----------------------------------------------------------------------------------------
>
> Key: METRON-1434
> URL: https://issues.apache.org/jira/browse/METRON-1434
> Project: Metron
> Issue Type: Improvement
> Affects Versions: 0.4.3
> 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
> Reporter: ashah
> Assignee: ashah
> Priority: Minor
> Labels: AWS, EC2, vagrant
> Fix For: 0.4.3
>
>
> 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.
> _Instructions:_
> [https://github.com/as22323/metron/blob/master/metron-deployment/README.md#aws-single-node-cluster-deployment-using-vagrant]
>
> *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.
> _Instructions:_
> [https://github.com/as22323/metron/blob/master/metron-deployment/README.md#aws-single-node-cluster-deployment-using-an-ami]
>
> ****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]
> [https://github.com/as22323/metron/blob/master/metron-deployment/development/aws-centos6/Vagrantfile]
> [changing eth1 to eth0]
> [https://github.com/as22323/metron/blob/master/metron-deployment/development/aws-centos6/inventory/group_vars/all]
>
>
> *"How the change may be verified: "*
> You should be able to see Ambari after following instructions
> (http://<elasticip>:8080)
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
