Skip to content
This repository has been archived by the owner on Jun 30, 2020. It is now read-only.

Speed up vv delete by only calling vagrant halt when necessary #194

Closed
jb510 opened this issue Dec 7, 2015 · 0 comments · Fixed by #195
Closed

Speed up vv delete by only calling vagrant halt when necessary #194

jb510 opened this issue Dec 7, 2015 · 0 comments · Fixed by #195

Comments

@jb510
Copy link
Collaborator

jb510 commented Dec 7, 2015

Currently vv delete calls vagrant halt which can be very slow even when vagrant isn't currently up.

We should find a reliable way to quickly check if vagrant is powered up and only then send a vagrant halt.

vagrant global-status returns quicker than vagrant status, but both can be pretty slow.

Suggesting we use:
VBoxManage list runningvms
but this is VirtualBox only (Do we support VMWare as a provider?)
jb510 added a commit that referenced this issue Dec 7, 2015
@jb510
Check VVV is running before trying to Halt #194
9fdd495
jb510 added a commit that referenced this issue Dec 7, 2015
@jb510
Move vagrant_maybe_halt to vagrant functions, use for create as well …
9bf43c7 
…as delete #194
jb510 added a commit that referenced this issue Dec 7, 2015
@jb510
Adds vagrant_maybe_halt, test is VVV is running before running time c…
0690eb4 
…onsuming `vagrant halt` closes #194
@jb510 jb510 mentioned this issue Dec 7, 2015
Merged
@bradp bradp closed this as completed in #195 Dec 7, 2015
@jb510 jb510 changed the title Speed up vv delete by only callign vagrant halt when necessary Speed up vv delete by only calling vagrant halt when necessary Dec 7, 2015
@jb510 jb510 mentioned this issue Dec 9, 2015
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Adds vagrant_maybe_halt bradp/vv
1 participant
@jb510