haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

doc: update ansible parallel provisioning tip 

As of Vagrant 1.7+, the ansible parallel provisioning trick is easier to
be implemented with `config.ssh.insert_key=false` (fallback to previous
behaviour).

Close #5048

[ci skip]
This commit is contained in:
Gilles Cornu 2015-01-12 10:23:13 +01:00
parent 9d74dcdb3d
commit fafaa00391
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
website/docs/source/v2/provisioning/ansible.html.md
View File

@ -207,6 +207,11 @@ by the sudo command.
Vagrant is designed to provision [multi-machine environments](/v2/multi-machine) in sequence, but the following configuration pattern can be used to take advantage of Ansible parallelism:
```
# By default, Vagrant 1.7+ automatically inserts a different insecure keypair
# for each new VM created. The easiest way to use the same keypair for all
# the machines is to disable this feature and rely on the legacy insecure key.
config.ssh.insert_key = false
config.vm.define 'machine2' do |machine|
machine.vm.hostname = 'machine2'
machine.vm.network "private_network", ip: "192.168.77.22"