You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "David M. Lyle (JIRA)" <ji...@apache.org> on 2016/09/29 14:48:20 UTC

[jira] [Commented] (METRON-474) Vagrant's default behavior should work as expected.

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

David M. Lyle commented on METRON-474:
--------------------------------------

[~ottobackwards] - I can't yet assign these to you, so I've assigned it to me to indicate it's in work.

[~james.sirota] - Do I have the ability to add people to the list of assignment candidates? If so, can you point me to how? Thanks!

> 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)