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
I looked at the issues and added my own evaluation of these tickets.
I would probably recommend to use numbers corresponding to low(1)-medium(2)-high(3) value and use some excel like document to have average value in some summary row.
Something like the structure bellow (I will use the CSV format delimited by ;): Issue #;Name;Url;Trouble;Gain;Note;
And this filled with my own prioritization: 8455;Move mailman to newer release of Fedora or CentOS;https://pagure.io/fedora-infrastructure/issue/8455;3;2;I see that the mailman needs multiple changes to be moved to RHEL 8. It will be nice to have that, but the gain is not that high.;
Just my 2c. This will make most of the work with data automatic and you could even use the document as input for some tagger script, that will tag the tickets.
Regards, Michal
On 09/03/2020 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
I see that the mailman needs multiple changes to be moved to RHEL 8. It will be nice to have that, but the gain is not that high.
Trouble : high Gain : medium
#8167 Adding topic authorization to our RabbitMQ instances - https://pagure.io/fedora-infrastructure/issue/8167
This sounds like most of the work is done, so I say low trouble. It will solve possible security issue, so I will go with medium-gain.
Trouble : low Gain : medium
#8035 A few final ansible secrets for kerneltest - https://pagure.io/fedora-infrastructure/issue/8035
I think this shouldn't be that much trouble to add a few other variables. Not sure how much gain we get for this, so I will go with low.
Trouble : low Gain : low
#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.
Trouble : high Gain : low
#7919 Fix fas fedmsg sending in openshift - https://pagure.io/fedora-infrastructure/issue/7919
We will replace FAS soon and fedmsg should be replaced by fedora-messaging. So low gain and high-trouble.
Trouble : high Gain : low
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-leave@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.fedorapro...
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.
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.
On Tue, 10 Mar 2020 at 02:45, Adam Williamson adamwill@fedoraproject.org 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-leave@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.fedorapro...
Just my thoughts:
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 : high Gain : high
This one blocks other two issues and as reported in comments the currently deployed version suffers of at least one XSS leak, so I would mark as really high priority. But if we have to put very high effort to fix it, it could be better to make the effort to upgrade to mailman3 that is actively developed.
#8167 Adding topic authorization to our RabbitMQ instances - https://pagure.io/fedora-infrastructure/issue/8167 Trouble : low Gain : medium
It seems the only things left are to adjust the config file and see if everything works in staging, so I'll mark low trouble.
#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 : ?
I see recent nightlies of F32 and Rawhide in PDC, is it fixed?
#7919 Fix fas fedmsg sending in openshift - https://pagure.io/fedora-infrastructure/issue/7919 Trouble : ? Gain : low
fas is being replaced, I don't think it worths to have it fixed.
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
On Mon, 9 Mar 2020 at 14:20, Mattia Verga mattia@fedoraproject.org wrote:
Just my thoughts:
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 : high Gain : high
This one blocks other two issues and as reported in comments the currently deployed version suffers of at least one XSS leak, so I would mark as really high priority. But if we have to put very high effort to fix it, it could be better to make the effort to upgrade to mailman3 that is actively developed.
The effort is upgrading to mailman3 which is actively developed.. getting it and everything related to it packaged into RPMs is the problem.
#7919 Fix fas fedmsg sending in openshift - https://pagure.io/fedora-infrastructure/issue/7919 Trouble : ? Gain : low
fas is being replaced, I don't think it worths to have it fixed.
The issue is that we have to manually update password on various servers by telling a box to update its FAS db's. It is more a 'how much do you want to deal with people complaining they can't login to various services after updating keys or passwords'.
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-leave@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.fedorapro...
On Mon, Mar 09, 2020 at 02:47:47PM +0100, Clement Verna wrote:
Hi all,
Hi!
This is the first email with trying to better prioritize our backlog of ticket ( https://pagure.io/fedora-infrastructure/issues ).
Thanks for doing this!
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 : High. Gain : medium
I think this is kind of stalled, because it needs for us to have a mailman3 rpm that works in fedora/epel8. Right now in Fedora it's FTBFS and it's being worked on. Also, there's other parts like hyperkitty, etc that aren't packaged yet. So, I wonder if this might be better as an initative? since we need packaging, then deployment/testing then migration and finally hand off to production.
#8167 Adding topic authorization to our RabbitMQ instances - https://pagure.io/fedora-infrastructure/issue/8167
Trouble : low Gain : high
I think this should just need config, but abompard would be the one to ask. If so, we should do it soon and make sure it works, then we will need to upgrade prod.
#8035 A few final ansible secrets for kerneltest - https://pagure.io/fedora-infrastructure/issue/8035
Trouble : low Gain : low
First, I guess we should make sure jcline still needs this. ;) Next tho, we have https://pagure.io/fedora-infrastructure/issue/7743 which is a template for these requests. I think I orig stalled on this one waiting for that one to finish so we would be able to easily collect all the info on it we need to make it. So, perhaps it's worth moving 7743 to finish and using this one to test it?
#7935 Nightlies (Rawhide and Branched) not imported to PDC - https://pagure.io/fedora-infrastructure/issue/7935
Trouble : high Gain : low
Doing anything other than turning off pdc is fraught with peril. ;) That said, this is likely because we added flatpaks.
https://lists.fedoraproject.org/archives/list/releng-cron@lists.fedoraprojec... https://lists.fedoraproject.org/archives/list/releng-cron@lists.fedoraprojec... https://lists.fedoraproject.org/archives/list/releng-cron@lists.fedoraprojec...
And adamw can chime in on the gain here. ;) Hurray! Stakeholders!
#7919 Fix fas fedmsg sending in openshift - https://pagure.io/fedora-infrastructure/issue/7919
Trouble : medium Gain : high
This one is causing 2-3 people a week to wonder why their ssh key didn't update and ask around and finally ask smooge or I and we run the playbook to update it. It's anoying from a support side.
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 :-).
I think it's a great thing to start in on. ;)
kevin
On Mon, Mar 9, 2020 at 3:58 PM Kevin Fenzi kevin@scrye.com wrote:
On Mon, Mar 09, 2020 at 02:47:47PM +0100, Clement Verna wrote:
Hi all,
Hi!
This is the first email with trying to better prioritize our backlog of ticket ( https://pagure.io/fedora-infrastructure/issues ).
Thanks for doing this!
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 : High. Gain : medium
I think this is kind of stalled, because it needs for us to have a mailman3 rpm that works in fedora/epel8. Right now in Fedora it's FTBFS and it's being worked on. Also, there's other parts like hyperkitty, etc that aren't packaged yet. So, I wonder if this might be better as an initative? since we need packaging, then deployment/testing then migration and finally hand off to production.
It seems that Duck (cc'd to this mail) has updated packaging for the stack, but we need to get mailman3 working again in Fedora and then branch that into EPEL 8. I've also been slowly churning through building hyperkitty and postorious packages based on the latest releases as opposed to our old release, but that's all blocked on mailman3 right now.
It'd be great to get some help with getting some of the new dependencies packaged in Fedora, too.
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 :-).
I think it's a great thing to start in on. ;)
It's a good start for sure. I'd also like to point out that we're close on getting pagure in EPEL 8, I'm waiting on pygit2[1] and celery[2] to show up in EPEL 8 now. If anyone can get in touch with either Pete Walter or Matthias Runge to help make this happen, that'd be very helpful.
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1803544 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1804511
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&tags=high-tro...
On Mon, 9 Mar 2020 at 14:47, Clement Verna cverna@fedoraproject.org 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@lists.fedoraproject.org