Here's my thoughts on rhel9 upgrades. We have 188 RHEL7 or RHEL8 instances (counting both vm's and bare hardware). Some of them I think we can reinstall anytime: backup01.iad2.fedoraproject.org batcave13.iad2.fedoraproject.org cloud-noc-os01.rdu-cc.fedoraproject.org dl01.iad2.fedoraproject.org dl02.iad2.fedoraproject.org dl03.iad2.fedoraproject.org dl04.iad2.fedoraproject.org dl05.iad2.fedoraproject.org download-ib01.fedoraproject.org download-rdu-cc01.fedoraproject.org dedicationsolutions01.iad2.fedoraproject.org ibiblio01.iad2.fedoraproject.org ibiblio05.iad2.fedoraproject.org memcached01.iad2.fedoraproject.org noc01.iad2.fedoraproject.org noc02.fedoraproject.org ns01.iad2.fedoraproject.org ns02.iad2.fedoraproject.org ns02.fedoraproject.org ns13.rdu2.fedoraproject.org osuosl01.fedoraproject.org secondary01.iad2.fedoraproject.org smtp-mm-ib01.fedoraproject.org smtp-mm-osuosl01.fedoraproject.org smtp-mm-cc-rdu01.fedoraproject.org storinator01.rdu-cc.fedoraproject.org sundries01.iad2.fedoraproject.org sundries02.iad2.fedoraproject.org tang01.iad2.fedoraproject.org tang02.iad2.fedoraproject.org torrent02.fedoraproject.org unbound-cc-rdu01.fedoraproject.org unbound-cc-rdu01.fedoraproject.org Some of them we can do, but we will need an outage for them: bastion01.iad2.fedoraproject.org bastion02.iad2.fedoraproject.org bastion13.iad2.fedoraproject.org people02.fedoraproject.org db01.iad2.fedoraproject.org db03.iad2.fedoraproject.org db-datanommer.iad2.fedoraproject.org db-koji.iad2.fedoraproject.org db-openq.iad2.fedoraproject.org (we can see how long the upgrade takes in stg on the various db servers) Some of them need applications/packages built for rhel9 and we can't do them until that is sorted out: badges (hopefully now ongoing?) notifs (ongoing) mm- (is mirrormanager2 ready to branch/build for rhel9?) pagure (how about pagure?) pkgs (also need pagure) sign (needs the new sigul. I'll ping patrick about it again) value* - needs limnoria in epel9 and fedmsg-irc replacement somehow. The zodbot part perhaps could be moved to openshift. Some we need to carefully save local data and restore after reinstall: batcave01.iad2.fedoraproject.org log01.iad2.fedoraproject.org The vmhosts need some investigation to see if we can reinstall and keep the vm data around. Otherwise we need to migrate vm's off and back on. I tried this in a early 9.0 install and it didn't seem to work on the host I was testing with, but should try again. qvmhost bvmhost vmhost* Some, we need to talk about: db-fas01 - this used to have the fas db on it to be more secure (seperate from db01), now all it has is the ipsilon db. I guess we could rename it db-ipsilon01? or fold it into db01? ipa - I think, but want to confirm we can just reinstall one replica with rhel9, get it all synced and then do another and another until the entire cluster is rhel9. rabbitmq - currently we are using rhel8 + openstack 16 repo. I suppose we can just go to rhel9 + openstack 17 repo. Some will just not move anytime soon: 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. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
