4b9d1a88bd
We have two standalone roles, puppet and cloud-launcher, but we currently install them with galaxy so depends-on patches don't work. We also install them every time we run anything, even if we don't need them for the playbook in question. Add two roles, one to install a set of ansible roles needed by the host in question, and the other to encapsulate the sequence of running puppet, which now includes installing the puppet role, installing puppet, disabling the puppet agent and then running puppet. As a followup, we'll do the same thing with the puppet modules, so that we arent' cloning and rsyncing ALL of the puppet modules all the time no matter what. Change-Id: I69a2e99e869ee39a3da573af421b18ad93056d5b
22 lines
587 B
YAML
22 lines
587 B
YAML
- hosts: "afs:afsdb:!disabled"
|
|
name: "AFS: run puppet on the AFS servers"
|
|
strategy: free
|
|
roles:
|
|
- run-puppet
|
|
|
|
- hosts: "mirror-update:!disabled"
|
|
name: "Create key for remote vos release"
|
|
tasks:
|
|
# Note done as root because all the update scripts run as root
|
|
- name: Create vos release keypair
|
|
openssh_keypair:
|
|
path: /root/.ssh/id_vos_release
|
|
type: ed25519
|
|
register: vos_release_keypair
|
|
|
|
# Note: relies on vos_release_keypair installed to mirror above
|
|
- hosts: "afs:!disabled"
|
|
name: "Allow remote vos_release"
|
|
roles:
|
|
- vos-release
|