Re: RHEL9 migration
On Tue, 2022-09-27 at 09:00 -0400, Stephen Smoogen wrote: > On Mon, 26 Sept 2022 at 17:56, Kevin Fenzi wrote: > > > Here's my thoughts on rhel9 upgrades. > > > > We have 188 RHEL7 or RHEL8 instances (counting both vm's and bare > > hardware). > > > > > > Some will just not move anytime soon: > > > > > Is it possible to look at these as 'why does this need fedmsg?' 'what > happens if it doesn't have fedmsg', and 'do we need it?' FWIW, while I'm one of the holdouts on still needing PDC, I don't think anything I do with PDC relies on it publishing messages. Don't know if any other use cases of PDC do. I do think we need to sort out the key use cases of PDC before getting rid of it, but leaving it on RHEL 8 seems like it'd be a reasonable choice. We really ought to be able to sort out getting off PDC before RHEL 8 kicks the bucket. I'm kinda kicking the tires on a plan to move critpath handling into Bodhi at the moment, for one thing. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: RHEL9 migration
> badges (hopefully now ongoing?) Yes it is, i hope that i will complete the list about what should be done in 1 or 2 days. > Some will just not move anytime soon: > > busgateway - needs fedmsg, only in epel7 Just as an information, fedbadges project as well currently depends on fedmsg. But i think that it will not take too long to replace it with fedora-messaging. Replacing fedmsg with fedora-messaging on fedbadges project is one of the goals that i'm hoping to achieve as soon as i can. ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: RHEL9 migration
On Tue, Sep 27, 2022 at 3:20 PM Neal Gompa wrote: > > On Tue, Sep 27, 2022 at 3:01 PM Stephen Smoogen wrote: > > > > > > > > On Mon, 26 Sept 2022 at 17:56, Kevin Fenzi wrote: > >> > >> Here's my thoughts on rhel9 upgrades. > >> > >> We have 188 RHEL7 or RHEL8 instances (counting both vm's and bare > >> hardware). > >> > >> > >> Some will just not move anytime soon: > >> > > > > Is it possible to look at these as 'why does this need fedmsg?' 'what > > happens if it doesn't have fedmsg', and 'do we need it?' > > > > mailman01 is one where maybe not having it on fedmsg wouldn't be earth > > shattering but it also has the bigger problem of all its libraries being > > FTBFS in Fedora and being retired from there. At which point we go with 'do > > we need to run mailing lists?' > > > > The mailman stack is FTBFS on Fedora right now because of a single > library (python-aiosmtpd) not working properly because of changes in > the SSL module in Python 3.10. The whole stack can branch into RHEL 9 > just fine. > And apparently that issue was fixed. Branching Mailman in EPEL9 is waiting on people adding infra-sig and epel-packagers-sig to dependencies of the stack. See: https://bugzilla.redhat.com/show_bug.cgi?id=2030061 -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: RHEL9 migration
On Tue, Sep 27, 2022 at 3:01 PM Stephen Smoogen wrote: > > > > On Mon, 26 Sept 2022 at 17:56, Kevin Fenzi wrote: >> >> Here's my thoughts on rhel9 upgrades. >> >> We have 188 RHEL7 or RHEL8 instances (counting both vm's and bare hardware). >> >> >> Some will just not move anytime soon: >> > > Is it possible to look at these as 'why does this need fedmsg?' 'what happens > if it doesn't have fedmsg', and 'do we need it?' > > mailman01 is one where maybe not having it on fedmsg wouldn't be earth > shattering but it also has the bigger problem of all its libraries being > FTBFS in Fedora and being retired from there. At which point we go with 'do > we need to run mailing lists?' > The mailman stack is FTBFS on Fedora right now because of a single library (python-aiosmtpd) not working properly because of changes in the SSL module in Python 3.10. The whole stack can branch into RHEL 9 just fine. >> >> busgateway - needs fedmsg, only in epel7 >> fedimg - needs fedmsg. will be replaced by some other solution >> github2fedmsg - needs fedmsg, only in epel7 >> mailman01 - needs fedmsg >> nuancer - needs fedmsg >> osbs - needs new container build system >> pdc - needs to be retired >> >> Finally, some I am not sure about and would like input: >> >> mbs - is this ready for rhel9? Should we move to Fedora instead? >> odcs - how about this? >> >> So, as far as help goes, getting mirrormanager2 and pagure all in epel9 >> would be great... >> coming up with a fedmsg-irc replacement, and getting limnoria in epel9 seem >> to be the best ways right now. >> I can start on the easier reinstalls. > Getting Pagure and MM2 branched into EPEL 9 shouldn't be too bad, hopefully. I did it the last go around for EPEL 8 with not too much effort. -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: RHEL9 migration
On Mon, 26 Sept 2022 at 17:56, Kevin Fenzi wrote: > Here's my thoughts on rhel9 upgrades. > > We have 188 RHEL7 or RHEL8 instances (counting both vm's and bare > hardware). > > > Some will just not move anytime soon: > > Is it possible to look at these as 'why does this need fedmsg?' 'what happens if it doesn't have fedmsg', and 'do we need it?' mailman01 is one where maybe not having it on fedmsg wouldn't be earth shattering but it also has the bigger problem of all its libraries being FTBFS in Fedora and being retired from there. At which point we go with 'do we need to run mailing lists?' > busgateway - needs fedmsg, only in epel7 > fedimg - needs fedmsg. will be replaced by some other solution > github2fedmsg - needs fedmsg, only in epel7 > mailman01 - needs fedmsg > nuancer - needs fedmsg > osbs - needs new container build system > pdc - needs to be retired > > Finally, some I am not sure about and would like input: > > mbs - is this ready for rhel9? Should we move to Fedora instead? > odcs - how about this? > > So, as far as help goes, getting mirrormanager2 and pagure all in epel9 > would be great... > coming up with a fedmsg-irc replacement, and getting limnoria in epel9 > seem to be the best ways right now. > I can start on the easier reinstalls. > -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
