Re: [PATCH] s3-mirror: fix missing trailing /

2020-03-16 Thread Stephen John Smoogen 
This is an FBR and I +1 it

On Mon, 16 Mar 2020 at 13:01, Kevin Fenzi  wrote:

> This is causing f31 updates to not be synced. The cron job reports:
>
> Subject: Cron  /usr/local/bin/lock-wrapper
> s3sync-updates-current "/usr/local/bin/s3-sync-path.sh
> /pub/fedora/linux/updates/31/Everything/x86_64/os" 2>&1 |
> /usr/local/bin/nag-once s3-updates-current.sh 1d 2>&1
>
> Syntax: /usr/local/bin/s3-sync-path.sh /pub/path/to/sync/
> NOTE! Path must end with a trailing /
>
> Signed-off-by: Kevin Fenzi 
> ---
>  roles/s3-mirror/tasks/main.yml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/roles/s3-mirror/tasks/main.yml
> b/roles/s3-mirror/tasks/main.yml
> index 5da7a02..395679b 100644
> --- a/roles/s3-mirror/tasks/main.yml
> +++ b/roles/s3-mirror/tasks/main.yml
> @@ -69,7 +69,7 @@
>
>  - name: s3sync cron - updates for current
>cron: name="s3sync-updates-current" minute="0" hour="3,9,15,21"
> user="s3-mirror"
> -job='/usr/local/bin/lock-wrapper s3sync-updates-current
> "/usr/local/bin/s3-sync-path.sh /pub/fedora/linux/updates/{{
> FedoraCycleNumber|int }}/Everything/x86_64/os" 2>&1 |
> /usr/local/bin/nag-once s3-updates-current.sh 1d 2>&1'
> +job='/usr/local/bin/lock-wrapper s3sync-updates-current
> "/usr/local/bin/s3-sync-path.sh /pub/fedora/linux/updates/{{
> FedoraCycleNumber|int }}/Everything/x86_64/os/" 2>&1 |
> /usr/local/bin/nag-once s3-updates-current.sh 1d 2>&1'
>  cron_file=s3-updates-current.sh
>when: env != 'staging' and
> inventory_hostname.startswith('mm-backend01.')
>tags:
> --
> 1.8.3.1
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>


-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: COVID-19 contingency plans for infra and release engineering

2020-03-16 Thread Kevin Fenzi 
On Mon, Mar 16, 2020 at 10:49:41AM -0400, Ben Cotton wrote:
> Hi teams,
> 
> As many of you already know, Red Hat has asked all employees to work
> from home. I know that many (most?) of you don't work from a Red Hat
> office normally (particularly if you're not a Red Hat employee!), but
> I want to check on the impact that an extended shutdown might have on
> the infrastructure, particularly the release engineering activities as
> we approach the Fedora 32 GA (currently scheduled for 21 April).

Yeah, all the infrastructure and releng folks are already remote. 

So, I don't think this will have too much impact. 
 
> In addition, what are our personnel risks? For example, if Mohan gets
> too sick to work, do we have enough shared knowledge and access to cut
> a release?

Yep. I think we do. I think we have at least 2 folks able to do any one
thing (of course it would be good to increase this number). 
> 
> Obviously, everyone is going to be impacted in some way, even if none
> of us get sick. This is a stressful and uncertain time. I've made it
> clear to Fedora and Red Hat leadership that we will continue with the
> schedule, but that the priority is the health of our community
> members. I don't want anyone working beyond what's reasonable for
> their personal situation. I just need to understand the risks so we
> can make plans to mitigate them or adjust the release schedule.

Yeah, it's really hard to predict. I hope after the next week or so we
will know more longer term impacts and settle into some kind of new 
'routine'.

kevin


signature.asc
Description: PGP signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

[PATCH] s3-mirror: fix missing trailing /

2020-03-16 Thread Kevin Fenzi 
This is causing f31 updates to not be synced. The cron job reports:

Subject: Cron  /usr/local/bin/lock-wrapper 
s3sync-updates-current "/usr/local/bin/s3-sync-path.sh 
/pub/fedora/linux/updates/31/Everything/x86_64/os" 2>&1 |
/usr/local/bin/nag-once s3-updates-current.sh 1d 2>&1

Syntax: /usr/local/bin/s3-sync-path.sh /pub/path/to/sync/
NOTE! Path must end with a trailing /

Signed-off-by: Kevin Fenzi 
---
 roles/s3-mirror/tasks/main.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/roles/s3-mirror/tasks/main.yml b/roles/s3-mirror/tasks/main.yml
index 5da7a02..395679b 100644
--- a/roles/s3-mirror/tasks/main.yml
+++ b/roles/s3-mirror/tasks/main.yml
@@ -69,7 +69,7 @@
 
 - name: s3sync cron - updates for current
   cron: name="s3sync-updates-current" minute="0" hour="3,9,15,21" 
user="s3-mirror"
-job='/usr/local/bin/lock-wrapper s3sync-updates-current 
"/usr/local/bin/s3-sync-path.sh /pub/fedora/linux/updates/{{ 
FedoraCycleNumber|int }}/Everything/x86_64/os" 2>&1 | /usr/local/bin/nag-once 
s3-updates-current.sh 1d 2>&1'
+job='/usr/local/bin/lock-wrapper s3sync-updates-current 
"/usr/local/bin/s3-sync-path.sh /pub/fedora/linux/updates/{{ 
FedoraCycleNumber|int }}/Everything/x86_64/os/" 2>&1 | /usr/local/bin/nag-once 
s3-updates-current.sh 1d 2>&1'
 cron_file=s3-updates-current.sh
   when: env != 'staging' and inventory_hostname.startswith('mm-backend01.')
   tags:
-- 
1.8.3.1
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: COVID-19 contingency plans for infra and release engineering

2020-03-16 Thread Mohan Boddu 
On Mon, Mar 16, 2020 at 10:51 AM Ben Cotton  wrote:
>
> Hi teams,
>
> As many of you already know, Red Hat has asked all employees to work
> from home. I know that many (most?) of you don't work from a Red Hat
> office normally (particularly if you're not a Red Hat employee!), but
> I want to check on the impact that an extended shutdown might have on
> the infrastructure, particularly the release engineering activities as
> we approach the Fedora 32 GA (currently scheduled for 21 April).

From RelEng side we are good, but there might be some issues with QA
as some tests are run manually on bare metal machines located at some
of our offices. People will not have access to these machines if the
offices are closed and maybe we have skip them for F32 GA.

>
> In addition, what are our personnel risks? For example, if Mohan gets
> too sick to work, do we have enough shared knowledge and access to cut
> a release?

Thanks Ben :)
But, I am working on updating the docs so that it will be easier for
either jednorozec or nirik to pick up the work.

>
> Obviously, everyone is going to be impacted in some way, even if none
> of us get sick. This is a stressful and uncertain time. I've made it
> clear to Fedora and Red Hat leadership that we will continue with the
> schedule, but that the priority is the health of our community
> members. I don't want anyone working beyond what's reasonable for
> their personal situation. I just need to understand the risks so we
> can make plans to mitigate them or adjust the release schedule.
>
>
> Thanks,
> BC
>
> --
> Ben Cotton
> He / Him / His
> Senior Program Manager, Fedora & CentOS Stream
> Red Hat
> TZ=America/Indiana/Indianapolis
> ___
> rel-eng mailing list -- rel-...@lists.fedoraproject.org
> To unsubscribe send an email to rel-eng-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/rel-...@lists.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

COVID-19 contingency plans for infra and release engineering

2020-03-16 Thread Ben Cotton 
Hi teams,

As many of you already know, Red Hat has asked all employees to work
from home. I know that many (most?) of you don't work from a Red Hat
office normally (particularly if you're not a Red Hat employee!), but
I want to check on the impact that an extended shutdown might have on
the infrastructure, particularly the release engineering activities as
we approach the Fedora 32 GA (currently scheduled for 21 April).

In addition, what are our personnel risks? For example, if Mohan gets
too sick to work, do we have enough shared knowledge and access to cut
a release?

Obviously, everyone is going to be impacted in some way, even if none
of us get sick. This is a stressful and uncertain time. I've made it
clear to Fedora and Red Hat leadership that we will continue with the
schedule, but that the priority is the health of our community
members. I don't want anyone working beyond what's reasonable for
their personal situation. I just need to understand the risks so we
can make plans to mitigate them or adjust the release schedule.


Thanks,
BC

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: Weekly Backlog Refinement - Week Mar 09 2020

2020-03-16 Thread Clement Verna 
Thanks all for your inputs and comments, this was really useful .

I have tagged these issues based on the feedback received, you can see all
the issues with at least one of these tags using this link [0]

[0] -
https://pagure.io/fedora-infrastructure/issues?status=Open=high-trouble=low-gain=high-gain=medium-gain=medium-trouble=low-trouble=0_status=

On Mon, 9 Mar 2020 at 14:47, Clement Verna  wrote:

> Hi all,
>
> This is the first email with trying to better prioritize our backlog of
> ticket ( https://pagure.io/fedora-infrastructure/issues ).
>
> So let's look at 5 tickets and rate them using the following categories :
> * low-trouble, medium-trouble, high-trouble
> * low-gain, medium-gain, high-gain
>
> #8455 Move mailman to newer release of Fedora or CentOS -
> https://pagure.io/fedora-infrastructure/issue/8455
> Trouble : ?
> Gain : ?
>
> #8167 Adding topic authorization to our RabbitMQ instances -
> https://pagure.io/fedora-infrastructure/issue/8167
> Trouble : ?
> Gain : ?
>
> #8035 A few final ansible secrets for kerneltest -
> https://pagure.io/fedora-infrastructure/issue/8035
> Trouble : ?
> Gain : ?
>
> #7935 Nightlies (Rawhide and Branched) not imported to PDC -
> https://pagure.io/fedora-infrastructure/issue/7935
> Trouble : ?
> Gain : ?
>
> #7919 Fix fas fedmsg sending in openshift -
> https://pagure.io/fedora-infrastructure/issue/7919
> Trouble : ?
> Gain : ?
>
>
> Let's also use this thread to ask questions and clarifications if needed.
> Also if you have any ideas or feedback on how to improve that process I am
> happy to hear about it :-).
>
>
> Thanks
> Clément
>
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: Weekly Backlog Refinement - Week Mar 09 2020

2020-03-16 Thread Clement Verna 
On Tue, 10 Mar 2020 at 02:45, Adam Williamson 
wrote:

> On Mon, 2020-03-09 at 17:00 +0100, Michal Konecny wrote:
> > > #7935 Nightlies (Rawhide and Branched) not imported to PDC -
> > > https://pagure.io/fedora-infrastructure/issue/7935
> > This is too much trouble for low gain, we should direct our manpower to
> > FPDC instead.
>
> This seems like a false evaluation to me. Presumably when FPDC is done,
> it will be populated by transferring in data from PDC. Garbage (or non-
> existence) in, garbage (or non-existence) out - if a bunch of data that
> should be in PDC is missing, it is not going to magically turn up when
> FPDC is deployed.
>

It is not clear yet how or when FPDC will be done (There is currently no
work happening on the replacement of PDC). The little work I did was to
look at the releng use cases and try to identify how we could use another
service to get the data we currently get from PDC which are mainly
information about component branches and state of releases. So we need to
also look at the other use cases of PDC and look at possible alternatives
that does not involved yet another application developed  by the Fedora
Community for example something like Kinto (https://github.com/Kinto/kinto)
might be a good fit.



> As noted in
> https://pagure.io/fedora-infrastructure/issue/7935#comment-631920 ,
> the last two official stable Fedora releases were not imported to PDC.
> That's pretty important archival information we're missing.
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org