From fafaa003916a8f7ca5006f9afa93d5dacf21caa6 Mon Sep 17 00:00:00 2001 From: Gilles Cornu Date: Mon, 12 Jan 2015 10:23:13 +0100 Subject: [PATCH] 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] --- website/docs/source/v2/provisioning/ansible.html.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/website/docs/source/v2/provisioning/ansible.html.md b/website/docs/source/v2/provisioning/ansible.html.md index 9301e0fb8..1648f7379 100644 --- a/website/docs/source/v2/provisioning/ansible.html.md +++ b/website/docs/source/v2/provisioning/ansible.html.md @@ -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"