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

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

GitHub user ottobackwards opened a pull request:

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

    METRON-474 - fix vagrant ansible defaults for quick and full

    Added defaults to match the run.sh parameters and removed the run.sh files. 
 Added a mention in the readmes as well.
    
    Now, instead of running run.sh and having to add parameters to vagrant 
provision, in both quick and full simply running vagrant up and vagrant 
provision will maintain the correct parameters.
    
    Tested by executing vagrant up and provision, vagrant ssh, ambari login

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ottobackwards/incubator-metron METRON-474

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

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

----


> Vagrant's default behavior should work as expected.
> ---------------------------------------------------
>
>                 Key: METRON-474
>                 URL: https://issues.apache.org/jira/browse/METRON-474
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: David M. Lyle
>            Assignee: David M. Lyle
>            Priority: Minor
>
> Currently, we maintain shell scripts to perform 'vagrant up' type activities.
> Let's:
> 1) Add sensible defaults to the Vagrantfile for full and quick dev
> 2) Verify that 'vagrant up', 'vagrant provision', and 'vagrant ssh' work as 
> expected.
> 3) Remove run.sh from both full and quick dev (note: I think 
> run_enrichment_role.sh and run_ansbile_role.sh should remain)
> 4) Update the documentation to reflect the changes  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to