Commit graph

21 commits

Author SHA1 Message Date
Rick Elrod
89acf4a7b9 try upping concurrency a bunch here
Signed-off-by: Rick Elrod <relrod@redhat.com>
2018-12-07 19:33:18 +00:00
Rick Elrod
52535a0fca log start/stop times so we can get an idea of how long each sync is taking
Signed-off-by: Rick Elrod <relrod@redhat.com>
2018-11-29 18:14:52 +00:00
Rick Elrod
5ead8fbd49 invalidate repomd.xml files after every sync
Signed-off-by: Rick Elrod <relrod@redhat.com>
2018-11-29 18:03:14 +00:00
Rick Elrod
759e01310d This is under /srv/ on this box
Signed-off-by: Rick Elrod <relrod@redhat.com>
2018-10-09 17:26:22 +00:00
Rick Elrod
cd814f8274 Future proof, so we do not sync 2x if there is ever a mm-backend02
Signed-off-by: Rick Elrod <relrod@redhat.com>
2018-10-09 17:20:52 +00:00
Rick Elrod
7984e52034 attempt at cron-ify-ing new s3 sync
Signed-off-by: Rick Elrod <relrod@redhat.com>
2018-10-09 17:17:53 +00:00
Patrick Uiterwijk
936e8b261a yum accepted pkg=, package calls it name=
Signed-off-by: Patrick Uiterwijk <patrick@puiterwijk.org>
2017-10-09 00:38:26 +02:00
Patrick Uiterwijk
039b08354a Yum allowed state=installed. Lets use state=present consistently
Signed-off-by: Patrick Uiterwijk <puiterwijk@redhat.com>
2017-10-08 22:31:03 +00:00
Patrick Uiterwijk
adcbf72f03 Packageize this, packageize that, packageize the world
Signed-off-by: Patrick Uiterwijk <puiterwijk@redhat.com>
2017-10-08 22:25:52 +00:00
Kevin Fenzi
745bcafcf8 no need to set this every playbook run 2017-02-04 18:35:50 +00:00
Kevin Fenzi
669c58b9a1 Try and make sure and send stderr on too so we don't get spammed 2015-12-08 20:32:31 +00:00
Adrian Reber
ea8b15e5d7 logrotate fails if files are not owned by root
Ignoring /etc/logrotate.d/s3-mirror because the file owner is wrong
(should be root).
2015-11-18 09:54:38 +00:00
Kevin Fenzi
90043a1ca4 Fix up quoting 2015-10-11 15:37:40 +00:00
Kevin Fenzi
4f2028866d Make s3 mirror only nag once per day. 2015-10-11 15:19:09 +00:00
Adrian Reber
36952cb189 Fix the s3sync report_mirror file names
The s3sync has been running successfully for some time now.
Unfortunately the last step, which runs report_mirror to update the
status of the s3 mirrors, failed as the report_mirror configuration
files had wrong names (missing .conf).
2015-09-11 20:00:15 +00:00
Adrian Reber
7efbd7f504 Fix s3sync and start it via cron.
This changes the s3sync setup at multiple places:

 * The s3sync script was using wrong paths which are now corrected
 * After the sync report_mirror was started which is now installed
 * The necessary report_mirror files are installed
 * The s3sync script is now running from cron instead as a service
 * Before touching any files fedmsg is queried to see if new files
   are available for syncing
 * logrotate has been adapted to the new setup
2015-08-20 18:36:07 +00:00
Kevin Fenzi
957c7c803d No need for mirrormanager-client here. 2015-07-27 19:47:29 +00:00
Kevin Fenzi
4237768025 These groups aren't there either. 2015-07-27 19:44:08 +00:00
Kevin Fenzi
3b11f96856 There's no apache user on mm-backend01, so no need to add s3sync to it's group. 2015-07-27 19:40:55 +00:00
Kevin Fenzi
2c5a5af8a1 Add s3-mirror role to mm-backend01
Add cron job for s3logs-sync, but disabled for now.
2015-07-27 19:37:54 +00:00
8c4931e0f9 most of s3-mirror role
Signed-off-by: Ricky Elrod <codeblock@fedoraproject.org>
2015-07-27 19:14:17 +00:00