It's possible for connectivity to a server or manifest application
to break for indeterminate periods of time, so the playbooks should
be run without errexit.
Change-Id: Id4968de3ef8090faa8f97ae8bab29c282d595bbc
The current set of runs make the fleet depend on all git changes
working. The only thing we actually care about is that gerrit doesn't
get updated if git fails.
Change-Id: Id488e14c7dbaddfbffece7b1d8ef65f06b3688d8
Previously the run_all.sh script would run puppet even if git is not
properly updated or if our puppet modules fail to install. Now set -e in
the script so that any failure to update git or install puppet modules
causes run_all.sh to bail out early.
This is important to ensure that we get consistent and expected results
from puppet when it runs.
Change-Id: Icb3fb2a97d11675762b49c57978b08115bfcbc04
Move the install location of the git checkout of the config repo
to /opt/system-config to make things more consistent for operators.
Actually moving this on the puppetmaster will be a manual step.
Change-Id: Id9297088ae6c76c02e35414433aae2733f9f639c
If the logic is just in a role, it's hard to re-use it in a one-off
manner on the command line. By putting it into a module, we can
run:
ansible git0* -m puppet
To run puppet on the git farm, for instance.
Also, the file is completely not openstack specific, so do it in
such a way that we can submit it as a module upstream.
Change-Id: I35b2850e02ec5da2b41ad14eec9fd6d5a356bc93
ansible-playbook is in /usr/local, but that's not in the cron job path.
Also, although there is an ansible log setting in ansible.cfg, the
ansible-playbook command still outputs stuff. We don't want cronspam,
so add the redirection to the log file back in.
Change-Id: Id585c11cca4cbd7e1ba26adbfbe22af650ca2b50
Instead of a shell script looping over ssh calls, use a simple
ansible playbook. The benefit this gets is that we can then also
script ad-hoc admin tasks either via playbooks or on the command
line. We can also then get rid of the almost entirely unused
salt infrastructure.
Change-Id: I53112bd1f61d94c0521a32016c8a47c8cf9e50f7
When we want to watch run_all happen, it's hard, because there is
no logging. To fix that - make there be some logging. Then, rotate
the logs.
Change-Id: I0eed7aeeec0ff21e58d57d6385cc59b74bbf31fb
In anticipation of driving puppet over ssh, we need keys on the hosts
and the scripts on the master. Don't turn them on yet, because we want
to be able to do some by-hand testing of the mechanism.
Change-Id: I2c353777e2f8fb5a2e733ce405ba40427ce901e5
