4 Commits

Author SHA1 Message Date
James E. Blair
2eee43e627 Name plays in playbooks
In run_all, we start a bunch of plays in sequence, but it's difficult
to tell what they're doing until you see the tasks.  Name the plays
themselves to produce a better narrative structure.

Change-Id: I0597eab2c06c6963601dec689714c38101a4d470
2018-09-07 10:51:56 -07:00
Monty Taylor
dfcd9c5403
Be explicit about where to install roles
The first entry is where ansible galaxy will install roles. We want that
to be /etc/ansible/roles, not overlaid on the system-config repo.

Pass --roles-path to ansible-galaxy to make sure they go to the right
place.

Change-Id: I109dc004acad32a515c6a1caca50ab38edc62aed
2018-08-17 13:09:59 -05:00
Monty Taylor
1a8c2f66da
Move /opt/system-config/production to /opt/system-config
The production directory is a relic from the puppet environment concept,
which we do not use. Remove it.

The puppet apply tests run puppet locally, where the production
environment is still needed, so don't update the paths in the
tools/prep-apply.sh.

Depends-On: https://review.openstack.org/592946
Change-Id: I82572cc616e3c994eab38b0de8c3c72cb5ec5413
2018-08-17 09:41:02 -05:00
Monty Taylor
815355bc83
Rename update_puppet to update-system-config
The purpose of the playbook is to update the system-config checkout, as
well as installing puppet modules and ansible roles.

Rename it, so that it's clearer what it does. Also, clean it up a bit.
We've gotten better at playbooks since we originally wrote this.

Change-Id: I793914ca3fc7f89cf019cf4cdf52acb7e0c93e60
2018-08-03 09:05:13 -05:00