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

vagrant-multi-machine #7

Closed
MatthewMi11er opened this issue Feb 2, 2015 · 3 comments
Closed

vagrant-multi-machine #7

MatthewMi11er opened this issue Feb 2, 2015 · 3 comments
Assignees

Comments

@MatthewMi11er
Copy link

To simplify the Ansible/Vagrant issue I created a basic provisioner which outputs the vagrant file to wherever you like. You can then run Ansible or Debops outside of Vagrant as normal. Using a custom provisioner means you don't need to create a dummy playbook, vagrant won't try to run Ansible at all and you can specify where you want the inventory to be created, so you don't have to use symlinks. It also means you don't have to deal with port numbers and ssh keys like you would with a hand-crafted inventory file.

I haven't yet fixed the issue of it running for each machine defined in the Vagrantfile , but doing so doesn't hurt anything and is easy to work around.

@drybjed
Copy link
Member

drybjed commented Feb 2, 2015

@MatthewMi11er Good to know! I'm really using Vagrant myself, preferring straight libvirt + KVM, but I'm sure some of my users will be interested.

@htgoebel
Copy link
Contributor

htgoebel commented Feb 5, 2015

This seams to be really great! I'm going to update the example soon.

@htgoebel htgoebel self-assigned this Feb 5, 2015
@htgoebel
Copy link
Contributor

Solved by #8 resp. e84c950

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

No branches or pull requests

3 participants