metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From JonZeolla <>
Subject [GitHub] incubator-metron pull request #560: METRON-912: Metron vagrant setup steps n...
Date Mon, 01 May 2017 19:48:42 GMT
GitHub user JonZeolla opened a pull request:

    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 ``, and we request ``.  This has been a specific
point of issue, although I have not tested ``.
    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]( 
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, as documented
[here]( and [here](
    ## 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](
for the complete guide to follow for contributions.  
    Please refer also to our [Build Verification Guidelines](
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](

    - [X] 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.
    - [X] Has your PR been rebased against the latest commit within the target branch (typically
    ### 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: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]( 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 METRON-912

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

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


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 or file a JIRA ticket
with INFRA.

View raw message