From 18b41ebda5da814adc01c264bc0ad2ae3264be7a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?N=C3=A1ndor=20Istv=C3=A1n=20Kr=C3=A1cser?= Date: Wed, 7 May 2014 11:24:28 +0200 Subject: [PATCH] Ansible inventory file location fixed according to the official Vagrant guide at http://docs.vagrantup.com/v2/provisioning/ansible.html --- docsite/rst/guide_vagrant.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docsite/rst/guide_vagrant.rst b/docsite/rst/guide_vagrant.rst index 3a15617e302..8dc8d10b449 100644 --- a/docsite/rst/guide_vagrant.rst +++ b/docsite/rst/guide_vagrant.rst @@ -93,8 +93,8 @@ Sometimes you may want to run Ansible manually against the machines. This is pretty easy to do. Vagrant automatically creates an inventory file for each Vagrant machine in -the same directory called ``vagrant_ansible_inventory_machinename``. It -configures the inventory file according to the SSH tunnel that Vagrant +the same directory located under ``.vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory``. +It configures the inventory file according to the SSH tunnel that Vagrant automatically creates, and executes ``ansible-playbook`` with the correct username and SSH key options to allow access. A typical automatically-created inventory file may look something like this: @@ -114,7 +114,7 @@ Here is an example: .. code-block:: bash - $ ansible-playbook -i vagrant_ansible_inventory_machinename --private-key=~/.vagrant.d/insecure_private_key -u vagrant playbook.yml + $ ansible-playbook -i .vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory --private-key=~/.vagrant.d/insecure_private_key -u vagrant playbook.yml .. seealso::