system-config/playbooks/roles/install-ansible
Monty Taylor c117c1106d Update install-ansible away from /opt/system-config
So that we can start running things from the zuul source rather
thatn update-system-config and /opt/system-config, we need to
install a few things onto the host in install-ansible so that the
ansible env is standalone.

This introduces a split execution path. The ansible config is
now all installed globally onto the machine by install-ansible
and does not reference a git checkout.

For running ad-hoc commands, an ansible.cfg is introduced inside
the root of the system-config dir. So if ansible-playbook is
executed with PWD==/opt/system-config it will find that ansible.cfg,
it will take precedence, and any content from system-config
will take precedence.

As a followup we'll make /opt/system-config/ansible.cfg written
out by install-ansible from the same template, and we'll update
the split to make ansible only work when executed from one of
the two configured locations, so that it's clear where we're
operating from.

Change-Id: I097694244e95751d96e67304aaae53ad19d8b873
2020-04-14 14:54:23 -05:00
..
defaults Add support for enabling the ARA callback plugin in install-ansible 2018-12-04 17:46:47 -05:00
files Update install-ansible away from /opt/system-config 2020-04-14 14:54:23 -05:00
tasks Update install-ansible away from /opt/system-config 2020-04-14 14:54:23 -05:00
templates Update install-ansible away from /opt/system-config 2020-04-14 14:54:23 -05:00
README.rst Add support for enabling the ARA callback plugin in install-ansible 2018-12-04 17:46:47 -05:00

README.rst

Install and configure Ansible on a host via pip

Role Variables