Weekly Backlog Refinement - Week Mar 30 2020

[Clement Verna]

Hi all,

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

#7867 Remove all old releases from torrent -
https://pagure.io/fedora-infrastructure/issue/7867
Trouble : ?
Gain : ?

#7880 email2fas not working in production (fedmsg/datanommer, fedmsg/irc) -
https://pagure.io/fedora-infrastructure/issue/7880
Trouble : ?
Gain : ?

#7743 Template for OIDC secret requests -
https://pagure.io/fedora-infrastructure/issue/7743
Trouble : ?
Gain : ?

#7796 oc rsh does not work -
https://pagure.io/fedora-infrastructure/issue/7796
Trouble : ?
Gain : ?

#7973 Finding a replacement for epylog -
https://pagure.io/fedora-infrastructure/issue/7973
Trouble : ?
Gain : ?

Thanks all

[Adam Williamson]

On Wed, 2020-04-01 at 15:50 +0200, Clement Verna wrote:
> Hi all,
>
> 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
>
> #7867 Remove all old releases from torrent -
> https://pagure.io/fedora-infrastructure/issue/7867
> Trouble : ?
> Gain : ?

low-gain
> #7880 email2fas not working in production (fedmsg/datanommer, fedmsg/irc) -
> https://pagure.io/fedora-infrastructure/issue/7880
> Trouble : ?
> Gain : ?

So the issues I see here are:

1) we're spewing out lots of email addresses in a very easily-
harvestable way (potentially if fixing this *properly* is hard, we
could obfuscate the email addresses in at least the human-readable
bits?)
2) anything like Badges which relies on these messages to associate an
event with a FAS identity probably isn't working (so Badges associated
with Bugzilla and possibly Pagure may not be working right)

so probably medium-gain ? trouble I can't estimate because (as
mentioned in ticket) I don't have access to the systems to find out why
it doesn't work.
> #7743 Template for OIDC secret requests -
> https://pagure.io/fedora-infrastructure/issue/7743
> Trouble : ?
> Gain : ?

low-trouble
low-gain (I'd say medium if there were *more* of these requests but I
don't see that there are any since 11 months ago)
> #7796 oc rsh does not work -
> https://pagure.io/fedora-infrastructure/issue/7796
> Trouble : ?
> Gain : ?
>
> #7973 Finding a replacement for epylog -
> https://pagure.io/fedora-infrastructure/issue/7973
> Trouble : ?
> Gain : ?

high-trouble (per smooge's comment)
medium-gain (since f29 is EOL and I'm guessing we'd like not to be on
RHEL 7 if we can avoid it?)

[Kevin Fenzi]

On Wed, Apr 01, 2020 at 03:50:19PM +0200, Clement Verna wrote:
> Hi all,
>
> 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
>
> #7867 Remove all old releases from torrent -
> https://pagure.io/fedora-infrastructure/issue/7867
> Trouble : ?
> Gain : ?

I looked at this, and... just did it. Took only a few minutes.
> #7880 email2fas not working in production (fedmsg/datanommer, fedmsg/irc) -
> https://pagure.io/fedora-infrastructure/issue/7880
> Trouble : ?
> Gain : ?

trouble: medium
gain: medium
> #7743 Template for OIDC secret requests -
> https://pagure.io/fedora-infrastructure/issue/7743
> Trouble : ?
> Gain : ?

Perhaps we should just drop this since we don't get that many requests?
but:

trouble: low
gain: low
> #7796 oc rsh does not work -
> https://pagure.io/fedora-infrastructure/issue/7796
> Trouble : ?
> Gain : ?

trouble: high
gain: low

This one is likely some apache/openshift/websockets thing. 
Not likely easy to debug.
> #7973 Finding a replacement for epylog -
> https://pagure.io/fedora-infrastructure/issue/7973
> Trouble : ?
> Gain : ?

Trouble: high
gain: high.

But I might be biased.

kevin

[Michal Konecny]

On 01/04/2020 15:50, Clement Verna wrote:
> Hi all,
>
> 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
>
> #7867 Remove all old releases from torrent - 
> https://pagure.io/fedora-infrastructure/issue/7867
> Trouble : ?
> Gain : ?

Skipping this one, because it was already solved by Kevin. Thanks Kevin.
> #7880 email2fas not working in production (fedmsg/datanommer, 
> fedmsg/irc) - https://pagure.io/fedora-infrastructure/issue/7880
> Trouble : medium
> Gain : low

Not sure about this one, FAS will be replaced soon, 
fedmsg_meta_fedora_infrastructure will go away with fedmsg. I think this 
is not worth our time, but we should instead think about including this 
into fedora messaging.

Regarding Anitya in this context: Anitya allows users to log in by other 
means than only FAS account, so this is probably why email2fas is used 
by it, but it's not necessary, if you don't use your FAS account you 
couldn't assume that you will be recognized by Anitya.
> #7743 Template for OIDC secret requests - 
> https://pagure.io/fedora-infrastructure/issue/7743
> Trouble : Low
> Gain : Low

I don't understand what is holding this ticket, it looks like the 
template needs only small adjustments. It's possible it's no longer 
valid, so then we should drop it. In each case it's low gain for low 
trouble.
> #7796 oc rsh does not work - 
> https://pagure.io/fedora-infrastructure/issue/7796
> Trouble : High
> Gain : Low

I think I saw this one in the past, but you could still use terminal in 
web interface. Also knowing OpenShift itself, this one will be hard to 
debug.
> #7973 Finding a replacement for epylog - 
> https://pagure.io/fedora-infrastructure/issue/7973
> Trouble : High
> Gain : High

Monitoring logs is something really useful for any troubleshooting, but 
the replacement wouldn't be easy to find.
> Thanks all
>
> infrastructure mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]...

[Adam Williamson]

On Thu, 2020-04-02 at 11:08 +0200, Michal Konecny wrote:
> > #7880 email2fas not working in production (fedmsg/datanommer, 
> > fedmsg/irc) - https://pagure.io/fedora-infrastructure/issue/7880
> > Trouble : medium
> > Gain : low
>
> Not sure about this one, FAS will be replaced soon, 
> fedmsg_meta_fedora_infrastructure will go away with fedmsg. I think this 
> is not worth our time, but we should instead think about including this 
> into fedora messaging.

Yeah, even if you replace the systems, the *feature* is still needed:
whether the lookup happens in FAS or AAA, whether the thing doing the
looking up is a fedmsg meta processor or a fedora-messaging schema,
"what Fedora account is associated with this email address?" is a thing
we need as long as we have messages from systems which give us email
addresses and not Fedora accounts (*cough cough* Bugzilla).

[Michal Konecny]

I don't talk about the need of the feature itself, I'm just saying that 
it's not worth to do the changes in the places that will be replaced anyway.

On 03/04/2020 22:04, Adam Williamson wrote:
> On Thu, 2020-04-02 at 11:08 +0200, Michal Konecny wrote:
> > > #7880 email2fas not working in production (fedmsg/datanommer,
> > > fedmsg/irc) - https://pagure.io/fedora-infrastructure/issue/7880
> > > Trouble : medium
> > > Gain : low
> >
> > Not sure about this one, FAS will be replaced soon,
> > fedmsg_meta_fedora_infrastructure will go away with fedmsg. I think this
> > is not worth our time, but we should instead think about including this
> > into fedora messaging.
>
> Yeah, even if you replace the systems, the *feature* is still needed:
> whether the lookup happens in FAS or AAA, whether the thing doing the
> looking up is a fedmsg meta processor or a fedora-messaging schema,
> "what Fedora account is associated with this email address?" is a thing
> we need as long as we have messages from systems which give us email
> addresses and not Fedora accounts (*cough cough* Bugzilla).