Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure only one Valkyrie VM is running at a time #46

Open
ergonlogic opened this issue Mar 16, 2015 · 3 comments
Open

Ensure only one Valkyrie VM is running at a time #46

ergonlogic opened this issue Mar 16, 2015 · 3 comments

Comments

@ergonlogic
Copy link
Member

We hard-code the IP address, among other things, so these kind of collisions will cause all kinds of hard-to-diagnose issues.

@ergonlogic
Copy link
Member Author

vagrant global-status provides us everything we need:

id       name     provider   state    directory                                                                   
------------------------------------------------------------------------------------------------------------------                  
e176eb1  valkyrie virtualbox poweroff /home/ergonlogic/vagrant/projects/13                                        
0bed096  valkyrie virtualbox poweroff /home/ergonlogic/vagrant/projects/15                                        
2892219  valkyrie virtualbox running  /home/ergonlogic/vagrant/projects/rel0    

Unfortunately, it doesn't yet implement the --machine-readable option: hashicorp/vagrant#4097

Still, it should be pretty easy to parse that, and loop over running VMs named 'valkyrie'.

@ergonlogic
Copy link
Member Author

This should probably happen in a pre-up hook.

@ergonlogic
Copy link
Member Author

Marking as postponed. We could work on that upstream issue, if we really want to push this forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant