[jira] [Commented] (METRON-912) Metron vagrant setup steps no longer work

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008105#comment-16008105
 ] 

ASF GitHub Bot commented on METRON-912:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-metron/pull/560


> Metron vagrant setup steps no longer work
> -
>
> Key: METRON-912
> URL: https://issues.apache.org/jira/browse/METRON-912
> Project: Metron
>  Issue Type: Improvement
>Reporter: Jon Zeolla
>
> The latest maven prereq steps no longer work, as they install versions 
> inconsistent with what we have tested.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (METRON-912) Metron vagrant setup steps no longer work

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004508#comment-16004508
 ] 

ASF GitHub Bot commented on METRON-912:
---

Github user JonZeolla commented on the issue:

https://github.com/apache/incubator-metron/pull/560
  
I gave `brew cask install docker` another shot this morning and got it 
running no problem.  Updated the instructions per discussion with @nickwallen.


> Metron vagrant setup steps no longer work
> -
>
> Key: METRON-912
> URL: https://issues.apache.org/jira/browse/METRON-912
> Project: Metron
>  Issue Type: Improvement
>Reporter: Jon Zeolla
>
> The latest maven prereq steps no longer work, as they install versions 
> inconsistent with what we have tested.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (METRON-912) Metron vagrant setup steps no longer work

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000776#comment-16000776
 ] 

ASF GitHub Bot commented on METRON-912:
---

Github user nickwallen commented on the issue:

https://github.com/apache/incubator-metron/pull/560
  
I tend to 'pin' my versions in Brew. I am more risk averse than you. ;)

But your argument sounds reasonable.   You convinced me.  If we start to 
get negative reports from users, we can always revisit.






> Metron vagrant setup steps no longer work
> -
>
> Key: METRON-912
> URL: https://issues.apache.org/jira/browse/METRON-912
> Project: Metron
>  Issue Type: Improvement
>Reporter: Jon Zeolla
>
> The latest maven prereq steps no longer work, as they install versions 
> inconsistent with what we have tested.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (METRON-912) Metron vagrant setup steps no longer work

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991416#comment-15991416
 ] 

ASF GitHub Bot commented on METRON-912:
---

GitHub user JonZeolla opened a pull request:

https://github.com/apache/incubator-metron/pull/560

METRON-912: Metron vagrant setup steps no longer work

## Contributor Comments
If you run the old steps you will install multiple inaccurate versions of 
tools:
1.  Maven `3.5.0` will be installed, but we specifically request people use 
`3.3.9`.
1.  Ansible latest is now `2.3.0.0`, and we request `2.2.2.0`.  This has 
been a specific point of issue, although I have not tested `2.3.0.0`.
1.  `brew cask install docker` does not install the components which we 
expect to exist, specifically the docker daemon.  I have only ever found the 
required components to be available when installing via their [install 
steps](https://docs.docker.com/engine/installation/).  Happy to be proven wrong 
on this one, but when I checked around with others, it seems everybody that 
I've spoken with actually follow these steps anyway.

I also purposefully removed some versioning granularity based off of 
experience, in hopes that this will continue to be accurate for a longer period 
of time.  For instance, I'm fairly certain any version of Python 2.7.x works 
just fine with Metron, and that the Vagrant and Virtualbox versions (as long as 
they are relatively new) are not an issue.

Note I removed the link to use the Ansible-provided instructions to install 
via brew because they do not support installing anything other than the latest 
(currently 2.3.0.0), as documented 
[here](https://github.com/caskroom/homebrew-cask/issues/25305) and 
[here](http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-pip).

## Testing
Uninstall the prereqs from your machine and install using the steps 
provided.  Spin up full-dev, quick-dev, etc. using the versions provided in the 
above steps.


## 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 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
  bin/generate-md.sh
  mvn site: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/JonZeolla/incubator-metron METRON-912

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-metron/pull/560.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 #560


commit 54596b85b95bce5bb869cc0272c9dc4cc6595b7c
Author: Jon Zeolla 
Date:   2017-05-01T19:29:32Z

METRON-912: Metron vagrant setup steps no longer work




> Metron vagrant setup steps no longer work
> -
>
> Key: METRON-912
> URL: https://issues.apache.org/jira/browse/METRON-912
> Project: Metron
>  Issue Type: Improvement
>Reporter: Jon Zeolla
>
> The latest maven prereq steps no longer work, as they install versions 
> inconsistent with what we have tested.