[
https://issues.apache.org/jira/browse/METRON-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532631#comment-15532631
]
David M. Lyle commented on METRON-472:
--------------------------------------
It's an important use case, I hate getting close to the end and then having to
start again. That's actually the reason for run_ansible_role.sh, give a
shortcut to re-starting from a given place. That said, it looks like I didn't
do a good job with defaults when I added the Ansible tags to the Vagrant file.
It wasn't my intention to alter the default Vagrant behavior. What would you
think about adding sensible defaults to the Vagrantfile so that vagrant up and
vagrant provision worked as one would expect?
> Vagrant Quick Dev should have both run.sh and runAgain.sh
> ---------------------------------------------------------
>
> Key: METRON-472
> URL: https://issues.apache.org/jira/browse/METRON-472
> Project: Metron
> Issue Type: Improvement
> Affects Versions: 0.2.1BETA
> Environment: Vagrant Quick Dev
> Reporter: Otto Fowler
>
> The vagrant quick dev is executed by running run.sh ( as opposed to just
> doing vagrant up in the full dev ). run.sh does the vagrant up, with the
> correct tags declared and the skip solr flag.
> Often the vagrant up does not finish execution, and as recommended you have
> to do a vagrant provision to continue.
> Depending on where in the process you have failed however, you will not
> succeed because you have not declared the same tags and skips.
> There should be another script to be run in the provision/retry case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
