On Thu, Mar 05, 2020 at 02:39:36PM -0800, Kevin Fenzi wrote:
> -CMD="aws s3 sync \
> +# first run do not delete anything or copy the repodata.
> +CMD1="aws s3 sync \
> + --exclude */repodata/* \
> + --exclude *.snapshot/* \
> + --exclude
On Thu, Mar 5, 2020, at 5:39 PM, Kevin Fenzi wrote:
> ok. Here's another cut at it.
>
LGTM
V/r,
James Cassell
> Attachments:
> * 0001-s3-mirror-Split-things-into-2-sync-runs-one-without-.patch
> * signature.asc
___
infrastructure mailing list --
On Thu, Mar 05, 2020 at 10:31:22PM +0100, Adrian Reber wrote:
> The only thing which is not clear in the documentation is when the
> delete is happening. With rsync there is an option '--delete-after' to
> make sure first all files are transferred and deletion happens
> afterwards. If 'aws s3
The only thing which is not clear in the documentation is when the
delete is happening. With rsync there is an option '--delete-after' to
make sure first all files are transferred and deletion happens
afterwards. If 'aws s3 sync' does the deletion during or before all
files are transferred you
+1 ok so the s3sync does allow for delete. I thought from previous
conversations it didn't work that way so my view of what was needed was
wrong.
On Thu, 5 Mar 2020 at 16:06, Kevin Fenzi wrote:
> First, I noticed we are running the full sync twice right now, at the
> same time:
>
>
First, I noticed we are running the full sync twice right now, at the
same time:
[root@mm-backend01 cron.d][PROD]# cat /etc/cron.d/s3.sh
#Ansible: s3sync
0 0,11 * * * s3-mirror /usr/local/bin/lock-wrapper s3sync /usr/local/bin/s3.sh
2>&1 | /usr/local/bin/nag-once s3.sh 1d 2>
&1
#Ansible:
The Fedora 32 Beta release readiness meeting will be held in
#fedora-meeting-1 at 19:00 UTC on Thursday 12 March. You can see it on
Fedocal at:
https://apps.fedoraproject.org/calendar/Fedora%20release/2020/3/12/#m9717
As a reminder, please ensure your team's readiness status is updated
on the
Hello,
Can somebody from web team take a look at this.
Just to clarify, we don't need a web page, we just want to use a
fedoraproject.org URL as namespace name and make sure everybody is OK
with it.
Thank you
On 2/27/20 3:59 PM, Tom Callaway wrote:
I would say if the web team is fine with
On Wed, Mar 04, 2020 at 11:52:44PM +, Kevin Fenzi wrote:
> We have been getting complaints from copr users that they are hitting
> out of date cloudfront cached data when they are doing builds.
> We are syncing not all that often currently, and sometimes if a updates
> push or rawhide compose
