I've added Prakash https://accounts.stg.fedoraproject.org/user/prakashmishra1598/ to the `sysadmin-openshift`, I'm not a sponsor for `sysadmin`, Kevin would you mind adding him there on staging please!
On Mon, 4 Jul 2022 at 09:02, David Kirwan <dkirwan@xxxxxxxxxx> wrote:
On Fri, 1 Jul 2022 at 17:14, Kevin Fenzi <kevin@xxxxxxxxx> wrote:On Fri, Jul 01, 2022 at 03:10:17PM +0100, David Kirwan wrote:
> haha looks like we've been living under a rock the pair of us.. the
> migration is fully complete, including the data? aha!
Yes, we are all done now. ;)
I even scaled fas2 / old accounts down to 0 yesterday and so far nothing
as blown up. ;)
It might have been easier with velero, but 90+% of our apps had no
persistent storage, so basically it was just scale down in old cluster,
deploy to new, change proxies to point to new cluster. The few that did
have storage, it was NFS, so that just added a 'chown data to new uid'
step.
Anyhow, I'm +1 to adding Prakash in stg for sure...
Thanks Kevin! Not to worry we learned a lot we'll write up what we learned anyway, from speaking to Mark O'Brien about it, this might come in handy in a future CentOS CI migration.I'll add Prakash to those two groups on stg.kevin
--
>
> On Fri, 1 Jul 2022 at 14:49, David Kirwan <dkirwan@xxxxxxxxxx> wrote:
>
> > Hi all,
> >
> > I'd like to propose Prakash be added to the `sysadmin` and
> > `sysadmin-openshift` groups on Staging. Prakash has lead the investigation
> > into Velero as a potential solution for our data migration, and also helped
> > with the Asknot app migration to Openshift 4. It would be nice to have
> > another person with experience in Openshift 4 in the community to help out!
> >
> > On Fri, 1 Jul 2022 at 14:27, Prakash Mishra <prakashmishra1598@xxxxxxxxx>
> > wrote:
> >
> >> Hi all,
> >>
> >> Over the last number of weeks we have been investigating a number of outstanding issues related to the Openshift 3/4 clusters managed by Fedora infrastructure. A large outstanding issue has been data migration. We've been investigating various solutions, and have come up with something which is relatively painless, and have verified it works with a proof of concept. So here is our proposal:
> >>
> >> ## Proposal
> >>
> >> - Using `Velero` https://velero.io/docs/main/migration-case/
> >> - From 3.11, plan to migrate only PV/PVC data
> >> - Velero will migrate multiple things, but the only thing we are interested is the PV data. So there might be a little clean up in a namespace once a migration has completed.
> >> - Once completed we can run our Fedora ansible playbooks as normal, the PVs/PVCs will be in place.
> >>
> >> If it sounds like a reasonable course of action we'll put a SOP together to describe how to carry out this work, and can either take it on ourselves or allow Infra and Releng in CPE to carry it out.
> >>
> >> Cheers,
> >> Prakash Mishra & David Kirwan.
> >>
> >> _______________________________________________
> >> 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 on the list, report it:
> >> https://pagure.io/fedora-infrastructure
> >>
> >
> >
> > --
> > David Kirwan
> > Software Engineer
> >
> > Community Platform Engineering @ Red Hat
> >
> > T: +(353) 86-8624108 IM: @dkirwan
> >
>
>
> --
> David Kirwan
> Software Engineer
>
> Community Platform Engineering @ Red Hat
>
> T: +(353) 86-8624108 IM: @dkirwan
> _______________________________________________
> 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 on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure
--David KirwanSoftware EngineerCommunity Platform Engineering @ Red Hat
T: +(353) 86-8624108 IM: @dkirwan
--
David Kirwan
Software Engineer
Community Platform Engineering @ Red Hat
T: +(353) 86-8624108 IM: @dkirwan
_______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
