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

Ansible: Try to document the limit breaking change

This commit is contained in:
Gilles Cornu 2014-02-17 22:34:38 +01:00
parent 709f3f4e6f
commit 17a4d75fd5
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -129,7 +129,6 @@ Vagrant.configure("2") do |config|
end end
``` ```
This causes Vagrant to run the `playbook.yml` playbook against all hosts in the inventory file.
Since an Ansible playbook can include many files, you may also collect the related files in Since an Ansible playbook can include many files, you may also collect the related files in
a directory structure like this: a directory structure like this:
@ -153,6 +152,13 @@ Vagrant.configure("2") do |config|
end end
``` ```
Vagrant will try to run the `playbook.yml` playbook against all machines defined in your Vagrantfile.
**Backward Compatibility Note**:
Up to Vagrant 1.4, the Ansible provisioner could potentially connect (multiple times) to all hosts from the inventory file.
This behaviour is still possible by setting `ansible.limit = 'all'` (see more details below).
## Additional Options ## Additional Options
The Ansible provisioner also includes a number of additional options that can be set, The Ansible provisioner also includes a number of additional options that can be set,
@ -174,7 +180,9 @@ all of which get passed to the `ansible-playbook` command that ships with Ansibl
* `ansible.sudo_user` can be set to a string containing a username on the guest who should be used * `ansible.sudo_user` can be set to a string containing a username on the guest who should be used
by the sudo command. by the sudo command.
* `ansible.ask_sudo_pass` can be set to `true` to require Ansible to prompt for a sudo password. * `ansible.ask_sudo_pass` can be set to `true` to require Ansible to prompt for a sudo password.
* `ansible.limit` can be set to a string or an array of machines or groups from the inventory file to further control which hosts are affected (e.g. useful to enable Ansible parallel execution). Note that as Vagrant 1.5, the machine name (taken from Vagrantfile) is set as default limit. * `ansible.limit` can be set to a string or an array of machines or groups from the inventory file to further control which hosts are affected. Note that:
* As Vagrant 1.5, the machine name (taken from Vagrantfile) is set as **default limit** to ensure that `vagrant provision` steps only affect the expected machine. Setting `ansible.limit` will override this default.
* Setting `ansible.limit = 'all'` can be used to make Ansible connects to all machines from the inventory file.
* `ansible.verbose` can be set to increase Ansible's verbosity to obtain detailed logging: * `ansible.verbose` can be set to increase Ansible's verbosity to obtain detailed logging:
* `'v'`, verbose mode * `'v'`, verbose mode
* `'vv'` * `'vv'`