From e0e01ddbe40de331bfe2d4e6d8d22c0f0a402d7b Mon Sep 17 00:00:00 2001 From: Ilkka Laukkanen Date: Sun, 3 Nov 2013 18:26:28 +0200 Subject: [PATCH] Clarify cobbler.py usage and testing instructions The doc incorrectly advised executing the static inventory, not the `cobbler.py` script. Also fixes minor language issue. --- docsite/rst/intro_dynamic_inventory.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docsite/rst/intro_dynamic_inventory.rst b/docsite/rst/intro_dynamic_inventory.rst index f0550a2a323..db2b9d39dd9 100644 --- a/docsite/rst/intro_dynamic_inventory.rst +++ b/docsite/rst/intro_dynamic_inventory.rst @@ -35,9 +35,9 @@ using Cobbler's XMLRPC API. To tie Ansible's inventory to Cobbler (optional), copy `this script `_ to /etc/ansible and `chmod +x` the file. cobblerd will now need to be running when you are using Ansible. -When running Ansible, to use this inventory, then path the script with the "-i /etc/ansible/cobbler.py" parameter. +When running Ansible, to use this inventory, execute ansible with the "-i /etc/ansible/cobbler.py" parameter. -First test the script by running `./etc/ansible/hosts` directly. You should see some JSON data output, but it may not have +First test the script by running `/etc/ansible/cobbler.py` directly. You should see some JSON data output, but it may not have anything in it just yet. Let's explore what this does. In cobbler, assume a scenario somewhat like the following::