Re: openshift 3->4 moves status and info needed
> However, fas is still there, so when we take down the cluster, badges > will break. Ideally we would fix that before we take down the old > cluster, but I don't want to leave it running there too long. > I'll check if there's an easyfix for badges' reliance on FAS. It may not be that much work. (famous last words) A. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
On Mon, Jun 27, 2022 at 10:19:51AM +0200, Michal Konecny wrote: > Is the automatic deployment from GitHub by webhook still an issue or was > this solved? You mean https://pagure.io/fedora-infrastructure/issue/10603 ? Not yet, but I will try and do that this week... 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
Is the automatic deployment from GitHub by webhook still an issue or was this solved? Michal On 24. 06. 22 23:19, Kevin Fenzi wrote: On Thu, Jun 23, 2022 at 05:45:49PM -0700, Kevin Fenzi wrote: ok. So we are down to: elections - moved in stg, but it crashes there. Bcotton was going to look, but he's dealing with a family emergency. Is anyone else able to take a look at it? It looks like it just doesn't start processing fast enough and openshift kills it. This was a port issue, got it fixed on the openshift side and it's moved now. fedocal - moved in stg, but authentication isn't working. It says that the 'redirect_uri' is invalid, but I cannot for the life of me see where. It looks right in config, it looks right on ipsilon. The prod one on openshift 3 looks the same. ;( Abompard: might you be able to take a look? Got this sorted with the help of Patrick and Darknao. Turns out the default in openshift 4 is for routers to 'append' the hostname on to proxy headers. Since the cluster is behind our already existing layer of proxies, it was re-writing the header to be application.fedoraproject.org.application.fedoraproject.org. Changing that to having it leave the forwarded header alone got it all working. fedocal is moved in prod and stg. koschei - mizdebsk was going to move this, but I might just try and do so tomorrow. I would think it would be pretty easy. mizdebsk went and did this this morning. koschei is all moved. So... thats it. All the things I know we want to keep are off the cluster. However, fas is still there, so when we take down the cluster, badges will break. Ideally we would fix that before we take down the old cluster, but I don't want to leave it running there too long. Thanks to everyone who helped get this done! Next step on openshift is some best practices, and look for an email from me listing what os versions we are using for each app (spoiler, we have a bunch of out of date ones). kevin ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
On Thu, Jun 23, 2022 at 05:45:49PM -0700, Kevin Fenzi wrote: > ok. So we are down to: > > elections - moved in stg, but it crashes there. Bcotton was going to > look, but he's dealing with a family emergency. Is anyone else able to > take a look at it? It looks like it just doesn't start processing fast > enough and openshift kills it. This was a port issue, got it fixed on the openshift side and it's moved now. > > fedocal - moved in stg, but authentication isn't working. It says that > the 'redirect_uri' is invalid, but I cannot for the life of me see > where. It looks right in config, it looks right on ipsilon. The prod one > on openshift 3 looks the same. ;( Abompard: might you be able to take a > look? Got this sorted with the help of Patrick and Darknao. Turns out the default in openshift 4 is for routers to 'append' the hostname on to proxy headers. Since the cluster is behind our already existing layer of proxies, it was re-writing the header to be application.fedoraproject.org.application.fedoraproject.org. Changing that to having it leave the forwarded header alone got it all working. fedocal is moved in prod and stg. > koschei - mizdebsk was going to move this, but I might just try and do > so tomorrow. I would think it would be pretty easy. mizdebsk went and did this this morning. koschei is all moved. So... thats it. All the things I know we want to keep are off the cluster. However, fas is still there, so when we take down the cluster, badges will break. Ideally we would fix that before we take down the old cluster, but I don't want to leave it running there too long. Thanks to everyone who helped get this done! Next step on openshift is some best practices, and look for an email from me listing what os versions we are using for each app (spoiler, we have a bunch of out of date ones). 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
ok. So we are down to: elections - moved in stg, but it crashes there. Bcotton was going to look, but he's dealing with a family emergency. Is anyone else able to take a look at it? It looks like it just doesn't start processing fast enough and openshift kills it. fedocal - moved in stg, but authentication isn't working. It says that the 'redirect_uri' is invalid, but I cannot for the life of me see where. It looks right in config, it looks right on ipsilon. The prod one on openshift 3 looks the same. ;( Abompard: might you be able to take a look? koschei - mizdebsk was going to move this, but I might just try and do so tomorrow. I would think it would be pretty easy. The following I haven't moved and unclear if we should: ? application-monitoring.yml I think this was an iniative a while back, but I'm not sure how it works. ? fas.yml I'd really like to kill it with fire. Ryan: any chance we can fix badges? :) ? monitor_dashboard.yml I think this was a POC/test/plaything. We can always redeploy later... Thats it, we are really close now... 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
Dne 17. 06. 22 v 16:07 Pierre-Yves Chibon napsal(a): On Fri, Jun 17, 2022 at 12:25:08PM +0200, Vít Ondruch wrote: Dne 15. 06. 22 v 1:49 Kevin Fenzi napsal(a): Greetings everyone. I finally had a quiet afternoon to really dig into the ocp3->4 migration. We have a total of 64 unique applications/projects over the 4 clusters (ocp3 prod/stg and ocp4 prod/stg). Of those 20 have been moved to ocp4 (either stg or prod or both). There's 4 that are sort of in the midst of moving to ocp4 prod, but need some more tweaking (flatpak-indexer, release-monitoring, discourse2fedmsg, transtats). I'd like to propose removing the following 9 entirely: REMOVE: simple-koji-ci.yml ( This was retired a long time ago) Does it mean that simple-koji-ci will be decommissioned soon? That is sad news. It has not been running for quite a while now. There is an equivalent service provided by the fedora-ci folks, so you shouldn't have seen it in any PR for a long time. Ah, so the "Fedora CI - scratch build" is something different. Good :) Thx for clarification. Vít Pierre ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure OpenPGP_signature Description: OpenPGP digital 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
On Tue, Jun 21, 2022 at 02:22:50PM +0200, Aurelien Bompard wrote: > > I've moved a bunch more projects the last few days. > > > > I've realized with datagrepper that we need to move apps that share a > virtualhost at the same time. Otherwise the SSLProxyCACertificateFile value > in the HTTP proxy will conflict and things will fail. > Luckily datagrepper only conflicted with kerneltest that we decided to drop > anyway, so I just disabled the proxy conf file for it on staging, but this > needs a proper app removal later. Huh, oddly I didn't hit this. It was working for me on friday (or thursday, whenever I moved it). ;( but yeah, we can try and avoid this... there's not too many vhosts we have that have more than one app in them. We long ago had a bunch under apps.fedoraproject.org, but since then they have all been split out. If we do see this more another way to fix it would be to put both CA's in one file and it should use either/both. 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
> I've moved a bunch more projects the last few days. > I've realized with datagrepper that we need to move apps that share a virtualhost at the same time. Otherwise the SSLProxyCACertificateFile value in the HTTP proxy will conflict and things will fail. Luckily datagrepper only conflicted with kerneltest that we decided to drop anyway, so I just disabled the proxy conf file for it on staging, but this needs a proper app removal later. A. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
REMOVE: fas-changes.yml > ( I think this was just needed for a short time for the account system > migration, please correct me if it's got some better use) > Correct, it can be dropped. > REMOVE: ipsilon.yml > ( we moved this to vm's because we couldn't run pam_sssd in openshift. > Has that changed?) > No, that's still the cas as far as I can tell, we need to keep it in a VM (unless we get permanent storage for openshift). A. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
> > > fas: I started to move this, but it's proving to be a lot of work and I > am not sure if it's worth it. Currently it's failing to build because > the epel6-infra dist repo is long gone. I could grab all the packages > from koji and make a new repo for this... but should I? > Badges is the only thing left that queries old fas. Can we fix it? > Or can I just break it if no one wants to fix it? > > I think Ryan started to look at this so its on the radar to be fixed at least ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
+1 for breaking that way we can fix / develop better if needed. On Fri, Jun 17, 2022, 5:22 PM Stephen Smoogen wrote: > > > On Fri, Jun 17, 2022 at 16:37 Kevin Fenzi wrote: > >> Replying to myself... >> >> I've moved a bunch more projects the last few days. >> >> Left to do are: >> >> docsbuilding.yml >> docstranslation.yml >> fedocal.yml >> fedora-packages-static.yml >> koschei.yml >> languages.yml >> nuancier.yml >> oraculum.yml >> review-stats.yml >> testdays.yml >> zezere.yml >> >> I'll do them next week. >> >> I've run into problems with: >> >> elections: staging pod starts up and then doesn't answer liveness probes >> and gets terminated. Perhaps pingou or bcotton could figure that out? >> I left prod alone for now until this is sorted. >> >> monitor_gating: This isn't working in staging due to a keytab issue. >> I tried various things to make it regenerate and use the right name, but >> it's not seeming to work. If anyone knows that app, feel free to look. >> I didn't move prod yet. >> >> fas: I started to move this, but it's proving to be a lot of work and I >> am not sure if it's worth it. Currently it's failing to build because >> the epel6-infra dist repo is long gone. I could grab all the packages >> from koji and make a new repo for this... but should I? >> Badges is the only thing left that queries old fas. Can we fix it? >> Or can I just break it if no one wants to fix it? >> > > I vote for breaking it as that is usually the impetus to getting it fixed > > > >> kevin >> ___ >> 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 on the list, report it: >> https://pagure.io/fedora-infrastructure >> > -- > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
On Fri, Jun 17, 2022 at 16:37 Kevin Fenzi wrote: > Replying to myself... > > I've moved a bunch more projects the last few days. > > Left to do are: > > docsbuilding.yml > docstranslation.yml > fedocal.yml > fedora-packages-static.yml > koschei.yml > languages.yml > nuancier.yml > oraculum.yml > review-stats.yml > testdays.yml > zezere.yml > > I'll do them next week. > > I've run into problems with: > > elections: staging pod starts up and then doesn't answer liveness probes > and gets terminated. Perhaps pingou or bcotton could figure that out? > I left prod alone for now until this is sorted. > > monitor_gating: This isn't working in staging due to a keytab issue. > I tried various things to make it regenerate and use the right name, but > it's not seeming to work. If anyone knows that app, feel free to look. > I didn't move prod yet. > > fas: I started to move this, but it's proving to be a lot of work and I > am not sure if it's worth it. Currently it's failing to build because > the epel6-infra dist repo is long gone. I could grab all the packages > from koji and make a new repo for this... but should I? > Badges is the only thing left that queries old fas. Can we fix it? > Or can I just break it if no one wants to fix it? > I vote for breaking it as that is usually the impetus to getting it fixed > kevin > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
Replying to myself... I've moved a bunch more projects the last few days. Left to do are: docsbuilding.yml docstranslation.yml fedocal.yml fedora-packages-static.yml koschei.yml languages.yml nuancier.yml oraculum.yml review-stats.yml testdays.yml zezere.yml I'll do them next week. I've run into problems with: elections: staging pod starts up and then doesn't answer liveness probes and gets terminated. Perhaps pingou or bcotton could figure that out? I left prod alone for now until this is sorted. monitor_gating: This isn't working in staging due to a keytab issue. I tried various things to make it regenerate and use the right name, but it's not seeming to work. If anyone knows that app, feel free to look. I didn't move prod yet. fas: I started to move this, but it's proving to be a lot of work and I am not sure if it's worth it. Currently it's failing to build because the epel6-infra dist repo is long gone. I could grab all the packages from koji and make a new repo for this... but should I? Badges is the only thing left that queries old fas. Can we fix it? Or can I just break it if no one wants to fix it? 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
On Fri, Jun 17, 2022 at 12:25:08PM +0200, Vít Ondruch wrote: > > Dne 15. 06. 22 v 1:49 Kevin Fenzi napsal(a): > > Greetings everyone. > > > > I finally had a quiet afternoon to really dig into the ocp3->4 > > migration. > > > > We have a total of 64 unique applications/projects over the 4 clusters > > (ocp3 prod/stg and ocp4 prod/stg). > > > > Of those 20 have been moved to ocp4 (either stg or prod or both). > > > > There's 4 that are sort of in the midst of moving to ocp4 prod, but need > > some more tweaking (flatpak-indexer, release-monitoring, > > discourse2fedmsg, transtats). > > > > I'd like to propose removing the following 9 entirely: > > REMOVE: simple-koji-ci.yml > >( This was retired a long time ago) > > > Does it mean that simple-koji-ci will be decommissioned soon? That is sad > news. It has not been running for quite a while now. There is an equivalent service provided by the fedora-ci folks, so you shouldn't have seen it in any PR for a long time. Pierre 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
Dne 15. 06. 22 v 1:49 Kevin Fenzi napsal(a): Greetings everyone. I finally had a quiet afternoon to really dig into the ocp3->4 migration. We have a total of 64 unique applications/projects over the 4 clusters (ocp3 prod/stg and ocp4 prod/stg). Of those 20 have been moved to ocp4 (either stg or prod or both). There's 4 that are sort of in the midst of moving to ocp4 prod, but need some more tweaking (flatpak-indexer, release-monitoring, discourse2fedmsg, transtats). I'd like to propose removing the following 9 entirely: REMOVE: simple-koji-ci.yml ( This was retired a long time ago) Does it mean that simple-koji-ci will be decommissioned soon? That is sad news. Vít OpenPGP_signature Description: OpenPGP digital 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
On Wed, Jun 15, 2022 at 09:39:34AM +0200, Michal Konecny wrote: > Hi Kevin, > > I agree with the removal of those 9 projects. Does those test projects have > any description? A few do... see below... > > And for info I want to work on the release-monitoring on prod soon, but not > sure when exactly this will happen. ok. I can help out if timezones permit. Oh, I almost forgot the main reason I wanted to send this! There's also some projects I have no idea about: ? application-monitoring.yml I think this may have been an iniative a while back, but not sure if this was completed, or just a test? ? monitor_dashboard.yml I think this was a proof of concept, but not sure. ? test-auth.yml I think this was to help debug some account system issue, and isn't needed anymore? > On 15. 06. 22 1:49, Kevin Fenzi wrote: > > Greetings everyone. > > > > I finally had a quiet afternoon to really dig into the ocp3->4 > > migration. > > > > We have a total of 64 unique applications/projects over the 4 clusters > > (ocp3 prod/stg and ocp4 prod/stg). > > > > Of those 20 have been moved to ocp4 (either stg or prod or both). > > > > There's 4 that are sort of in the midst of moving to ocp4 prod, but need > > some more tweaking (flatpak-indexer, release-monitoring, > > discourse2fedmsg, transtats). > > > > I'd like to propose removing the following 9 entirely: > > > > REMOVE: accountsystem.yml > >( an old proof of concept of noggin/caapi/etc) Not actually running, so no description. > > > > REMOVE: distgit_bugzilla_sync.yml > >( we do this in a toddler anymore) Description:Cron job syncing to bugzilla the default assignee and CC list set in dist-git > > REMOVE: fas-changes.yml > >( I think this was just needed for a short time for the account system > >migration, please correct me if it's got some better use) Not running. > > > > REMOVE: fas-stg.yml > >( Old account system staging, we can use the fas.yml playbook if we > >have to keep fas) Not running. > > REMOVE: ipsilon.yml > >( we moved this to vm's because we couldn't run pam_sssd in openshift. > >Has that changed?) Description:ipsilon > > > > REMOVE: kerneltest.yml > >( This never went into service and doesn't do exactly what kernel > >maintainers want ) Description:kerneltest > > REMOVE: sanitarium.yml > >( some test project? ) Not running. > > REMOVE: simple-koji-ci.yml > >( This was retired a long time ago) Not running. > > REMOVE: sso.yml > >( another test?) Description:sso kevin -- > > These 3 are broken in staging and need to be fixed before we can move > > them (I really like to see things run in stg before we move them to > > prod): > > > > BROKEN: compose-tracker.yml > > BROKEN: monitor_gating.yml > > BROKEN: transtats.yml > > > > I'll try and ping owners of these to look and fix them soon. > > > > That leaves: > > > > datagrepper.yml > > datanommer.yml > > docsbuilding.yml > > docstranslation.yml > > elections.yml (will wait for current elections to finish) > > fas.yml > > fedocal.yml > > fedora-packages-static.yml > > greenwave.yml > > koschei.yml > > languages.yml > > mdapi.yml > > messaging-bridges.yml > > nuancier.yml (I think this was a staging only proof of concept) > > oraculum.yml > > review-stats.yml > > testdays.yml > > toddlers.yml > > waiverdb.yml > > websites.yml > > zezere.yml > > > > I'll keep working on the list this week and hopefully we can get them > > all moved soon. :) > > > > kevin > > > > ___ > > 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 on the list, report it: > > https://pagure.io/fedora-infrastructure > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure 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
Re: openshift 3->4 moves status and info needed
Hi Kevin, I agree with the removal of those 9 projects. Does those test projects have any description? And for info I want to work on the release-monitoring on prod soon, but not sure when exactly this will happen. Michal On 15. 06. 22 1:49, Kevin Fenzi wrote: Greetings everyone. I finally had a quiet afternoon to really dig into the ocp3->4 migration. We have a total of 64 unique applications/projects over the 4 clusters (ocp3 prod/stg and ocp4 prod/stg). Of those 20 have been moved to ocp4 (either stg or prod or both). There's 4 that are sort of in the midst of moving to ocp4 prod, but need some more tweaking (flatpak-indexer, release-monitoring, discourse2fedmsg, transtats). I'd like to propose removing the following 9 entirely: REMOVE: accountsystem.yml ( an old proof of concept of noggin/caapi/etc) REMOVE: distgit_bugzilla_sync.yml ( we do this in a toddler anymore) REMOVE: fas-changes.yml ( I think this was just needed for a short time for the account system migration, please correct me if it's got some better use) REMOVE: fas-stg.yml ( Old account system staging, we can use the fas.yml playbook if we have to keep fas) REMOVE: ipsilon.yml ( we moved this to vm's because we couldn't run pam_sssd in openshift. Has that changed?) REMOVE: kerneltest.yml ( This never went into service and doesn't do exactly what kernel maintainers want ) REMOVE: sanitarium.yml ( some test project? ) REMOVE: simple-koji-ci.yml ( This was retired a long time ago) REMOVE: sso.yml ( another test?) These 3 are broken in staging and need to be fixed before we can move them (I really like to see things run in stg before we move them to prod): BROKEN: compose-tracker.yml BROKEN: monitor_gating.yml BROKEN: transtats.yml I'll try and ping owners of these to look and fix them soon. That leaves: datagrepper.yml datanommer.yml docsbuilding.yml docstranslation.yml elections.yml (will wait for current elections to finish) fas.yml fedocal.yml fedora-packages-static.yml greenwave.yml koschei.yml languages.yml mdapi.yml messaging-bridges.yml nuancier.yml (I think this was a staging only proof of concept) oraculum.yml review-stats.yml testdays.yml toddlers.yml waiverdb.yml websites.yml zezere.yml I'll keep working on the list this week and hopefully we can get them all moved soon. :) kevin ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
openshift 3->4 moves status and info needed
Greetings everyone. I finally had a quiet afternoon to really dig into the ocp3->4 migration. We have a total of 64 unique applications/projects over the 4 clusters (ocp3 prod/stg and ocp4 prod/stg). Of those 20 have been moved to ocp4 (either stg or prod or both). There's 4 that are sort of in the midst of moving to ocp4 prod, but need some more tweaking (flatpak-indexer, release-monitoring, discourse2fedmsg, transtats). I'd like to propose removing the following 9 entirely: REMOVE: accountsystem.yml ( an old proof of concept of noggin/caapi/etc) REMOVE: distgit_bugzilla_sync.yml ( we do this in a toddler anymore) REMOVE: fas-changes.yml ( I think this was just needed for a short time for the account system migration, please correct me if it's got some better use) REMOVE: fas-stg.yml ( Old account system staging, we can use the fas.yml playbook if we have to keep fas) REMOVE: ipsilon.yml ( we moved this to vm's because we couldn't run pam_sssd in openshift. Has that changed?) REMOVE: kerneltest.yml ( This never went into service and doesn't do exactly what kernel maintainers want ) REMOVE: sanitarium.yml ( some test project? ) REMOVE: simple-koji-ci.yml ( This was retired a long time ago) REMOVE: sso.yml ( another test?) These 3 are broken in staging and need to be fixed before we can move them (I really like to see things run in stg before we move them to prod): BROKEN: compose-tracker.yml BROKEN: monitor_gating.yml BROKEN: transtats.yml I'll try and ping owners of these to look and fix them soon. That leaves: datagrepper.yml datanommer.yml docsbuilding.yml docstranslation.yml elections.yml (will wait for current elections to finish) fas.yml fedocal.yml fedora-packages-static.yml greenwave.yml koschei.yml languages.yml mdapi.yml messaging-bridges.yml nuancier.yml (I think this was a staging only proof of concept) oraculum.yml review-stats.yml testdays.yml toddlers.yml waiverdb.yml websites.yml zezere.yml I'll keep working on the list this week and hopefully we can get them all moved soon. :) 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
