fbb9790d49
This is a migration of the current periodic "vos release" script to mirror-update.opendev.org. The current script is deployed by puppet and run by a cron job on afsdb01.dfw.openstack.org. My initial motivation for this was wanting to better track our release of these various volumes. With tarballs and releases moving to AFS publishing, we are going to want to track the release process more carefully. Initially, I wanted to send timing statistics to graphite so we could build a dashboard and track the release times of all volumes. Because this requires an additional libraries and since we are deprecating puppet, further development there is unappealing and it would better live in ansible. Since I6c96f89c6f113362e6085febca70d58176f678e7 we have the ability to call "vos release" with "-localauth" permissions via ssh on mirror-update; this avoids various timeout issues (see the changelog comment there for more details). So we do not need to run this script directly on the afsdb server. We are alreadying publishing mirror update logs from mirror-update, and it would be good to also publish these release logs so anyone can see if there are problems. All this points to mirror-update.opendev.org being a good future home for this script. The script has been refactored some to - have a no-op mode - send timing stats for each volume release - call "vos release" via the ssh mecahnism we created - use an advisory lock to avoid running over itself It runs from a virtualenv and it's logs are published via the same mechanism as the mirror logs (slightly misnamed now). Note this script is currently a no-op to test the deployment, running and log publishing. A follow-up will disable the old job and make this active. Change-Id: I62ae941e70c7d58e00bc663a50d52e79dfa5a684
10 lines
312 B
ReStructuredText
10 lines
312 B
ReStructuredText
afs-release
|
|
|
|
Install the script and related bits and pieces for periodic release of
|
|
various AFS volumes. This role is really only intended to be run on
|
|
the `mirror-update` host, as it uses the ssh-key installed by that
|
|
host to run `vos release` under `-localauth` on the remote AFS
|
|
servers.
|
|
|
|
**Role Variables**
|