gaschz/ansible-qubes
1
0
Fork 0
mirror of https://github.com/Rudd-O/ansible-qubes.git synced 2025-03-01 14:22:33 +01:00
Code Issues Packages Projects Releases Wiki Activity

test hyperlinking, 5

Browse Source
This commit is contained in:
Manuel Amador (Rudd-O) 2015-12-21 01:49:53 +00:00
parent d9fde907bd
commit f8128851a3
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
examples/ansible/README.md
View File

@ -20,18 +20,18 @@ Ansible configuration
The starting point is the file [`ansible.cfg`](./ansible.cfg). This file tells Ansible where The starting point is the file [`ansible.cfg`](./ansible.cfg). This file tells Ansible where
to find the requisite components to make the Qubes automation work. As to find the requisite components to make the Qubes automation work. As
you can see, it's composed mostly of paths, and it points you to the `hosts` you can see, it's composed mostly of paths, and it points you to the
file. [`hosts`](./hosts) file.
Importantly, because Ansible will look for the `ansible.cfg` file Importantly, because Ansible will look for the [`ansible.cfg`](./ansible.cfg) file
on your current directory first, that means you will be running your on your current directory first, that means you will be running your
Ansible commands on the directory containing `ansible.cfg`. Later, you can Ansible commands on the directory containing [`ansible.cfg`](./ansible.cfg). Later, you can
deploy aliases, symlinks or helpers to help you work around that. deploy aliases, symlinks or helpers to help you work around that.
Inventory Inventory
--------- ---------
The `hosts` file is your machine inventory -- the VMs (and also physical The [`hosts`](./hosts) file is your machine inventory -- the VMs (and also physical
machines) that you own, and how they group together. The included inventory machines) that you own, and how they group together. The included inventory
is almost certainly guaranteed not to match the machines you have, nor how is almost certainly guaranteed not to match the machines you have, nor how
you've grouped them conceptually, so feel free to edit it how you see fit. To you've grouped them conceptually, so feel free to edit it how you see fit. To
@ -52,8 +52,9 @@ How Ansible knows to connect to your Qubes VMs
---------------------------------------------- ----------------------------------------------
Importantly, nothing about this is magic. `qubes` in the `ansible_connection` Importantly, nothing about this is magic. `qubes` in the `ansible_connection`
parameter merely tells Ansible to use the `ansible/connection_plugins/qubes.py` parameter merely tells Ansible to use the
as pointed to by the `ansible.cfg` file. That file automatically enlists [Qubes connection plugin](../../ansible/connection_plugins/qubes.py)
as pointed to by the [`ansible.cfg`](./ansible.cfg) file. That file automatically enlists
the `bombshell-client` technology to connect you to your VMs via Ansible. the `bombshell-client` technology to connect you to your VMs via Ansible.
When `bombshell-client` starts, it attempts to connect to the target VM's When `bombshell-client` starts, it attempts to connect to the target VM's