2025-01-22 14:02:14 <@humaton:fedora.im> !startmeeting Git Forge Meeting
2025-01-22 14:02:15 <@meetbot:fedora.im> Meeting started at 2025-01-22 14:02:14 UTC
2025-01-22 14:02:16 <@meetbot:fedora.im> The Meeting name is 'Git Forge Meeting'
2025-01-22 14:03:02 <@amoloney:fedora.im> !hi
2025-01-22 14:03:03 <@zodbot:fedora.im> Aoife Moloney (amoloney)
2025-01-22 14:03:07 <@dherrera:fedora.im> !hi
2025-01-22 14:03:08 <@zodbot:fedora.im> Diego Herrera (dherrera) - he / him / his
2025-01-22 14:03:08 <@humaton:fedora.im> !info this is meeting about the migration effort of Fedora gitforge
2025-01-22 14:03:12 <@t0xic0der:fedora.im> !hi
2025-01-22 14:03:13 <@zodbot:fedora.im> Akashdeep Dhar (t0xic0der) - he / him / his
2025-01-22 14:03:16 <@humaton:fedora.im> !topic init
2025-01-22 14:03:17 <@ekidney:matrix.org> !hi
2025-01-22 14:03:20 <@zodbot:fedora.im> emma kidney (ekidney) - she / her / hers
2025-01-22 14:03:23 <@phsmoura:fedora.im> !hi
2025-01-22 14:03:24 <@zodbot:fedora.im> Pedro Moura (phsmoura) - he / him / his
2025-01-22 14:03:41 <@t0xic0der:fedora.im> !link https://docs.google.com/document/d/1DpiOvGbqcVrrafKmt9B1-bPrMthqoA0H31p-HzG0ywA/edit?usp=sharing
2025-01-22 14:04:04 <@patrikp:matrix.org> Hi. 👋
2025-01-22 14:04:10 <@humaton:fedora.im> !hi
2025-01-22 14:04:12 <@zodbot:fedora.im> Tomáš Hrčka (humaton) - he / him / his
2025-01-22 14:04:27 <@t0xic0der:fedora.im> I wonder if we should retain meeting notes separately or would the meeting summary/logs from the meetbot be sufficient. Thoughts?
2025-01-22 14:04:29 <@humaton:fedora.im> Can't access item
2025-01-22 14:04:45 <@humaton:fedora.im> notes will be kept by the bot here wont they?
2025-01-22 14:04:57 <@amoloney:fedora.im> do we need the doc? The bot should do just fone
2025-01-22 14:05:01 <@amoloney:fedora.im> *fine
2025-01-22 14:05:24 <@t0xic0der:fedora.im> Cool - Lets stick to the meetbot logs/summary then - I have added you to the doc though jednorozec 
2025-01-22 14:05:38 <@humaton:fedora.im> we have a repo for the meeting structure and org stuff https://codeberg.org/fedora/gitforge-migration/src/branch/main/meeting.md
2025-01-22 14:05:59 <@farchord:fedora.im> Yeah maybe not a good idea to use a google doc that's locked out XD
2025-01-22 14:06:26 <@lenkaseg:fedora.im> !hi
2025-01-22 14:06:28 <@zodbot:fedora.im> Lenka Segura (lenkaseg)
2025-01-22 14:06:43 <@humaton:fedora.im> we will have meeting notes if there is structure to the meeting. 
2025-01-22 14:06:53 <@mathstuf:matrix.org> !hi
2025-01-22 14:06:54 <@zodbot:fedora.im> No Fedora Accounts users have the @mathstuf:matrix.org Matrix Account defined
2025-01-22 14:07:13 <@mathstuf:matrix.org> hrm…will have to connect that up i guess
2025-01-22 14:07:41 <@humaton:fedora.im> !link https://codeberg.org/fedora
2025-01-22 14:08:11 <@humaton:fedora.im> there is a organization on Codeberg with repository for the meeting template 
2025-01-22 14:08:23 <@humaton:fedora.im> feel free to propose any changes/content
2025-01-22 14:08:51 <@humaton:fedora.im> lets move on 
2025-01-22 14:08:52 <@humaton:fedora.im> !topic Tickets and Updates
2025-01-22 14:09:02 <@humaton:fedora.im> !link https://pagure.io/fedora-infra/forgejo-deployment/issues
2025-01-22 14:09:09 <@mathstuf:matrix.org> !hi
2025-01-22 14:09:11 <@zodbot:fedora.im> None (mathstuf)
2025-01-22 14:09:12 <@humaton:fedora.im> We have few Epics to look at 
2025-01-22 14:10:22 <@Zlopez:matrix.org> !hi
2025-01-22 14:10:23 <@humaton:fedora.im> !link https://pagure.io/fedora-infra/forgejo-deployment/issue/1
2025-01-22 14:10:26 <@zodbot:fedora.im> Michal Konecny (zlopez)
2025-01-22 14:11:01 <@humaton:fedora.im> SO we need to build or reuse iamges for our FOrgejo deployment
2025-01-22 14:11:14 <@humaton:fedora.im> SO we need to build or reuse images for our Forgejo deployment
2025-01-22 14:11:57 <@humaton:fedora.im> I was thinking about using konflux to do that, there is a demo pipeline in the ticket
2025-01-22 14:12:17 <@humaton:fedora.im> naming is up for change I just wanted to get thing flowing from codeberg->konflux
2025-01-22 14:12:48 <@humaton:fedora.im> WDYT? how/where should we get our images for the deployment
2025-01-22 14:13:43 <@Zlopez:matrix.org> Could we use Fedora images as a base for Forgejo
2025-01-22 14:13:45 <@Zlopez:matrix.org> ?
2025-01-22 14:13:56 <@t0xic0der:fedora.im> Sounds good to me. Gives us a chance to take Konflux for a spin as well.
2025-01-22 14:14:06 <@thisisyaash:fedora.im> !hi
2025-01-22 14:14:06 <@zodbot:fedora.im> Yashwanth Rathakrishnan (thisisyaash)
2025-01-22 14:14:14 <@humaton:fedora.im> Well what do you mean? 
2025-01-22 14:14:31 <@humaton:fedora.im> the demo uses rawhide, so for sure we want to use fedora as base image
2025-01-22 14:14:44 <@humaton:fedora.im> but we need postgres image we need nginx for proxies
2025-01-22 14:14:49 <@humaton:fedora.im> we need a lot of service images
2025-01-22 14:14:55 <@Zlopez:matrix.org> That answers my question
2025-01-22 14:15:10 <@dkirwan:fedora.im> If its open to discussion, might be better to use rhel imo
2025-01-22 14:15:36 <@humaton:fedora.im> sure why? what? how?
2025-01-22 14:15:48 <@dkirwan:fedora.im> Much longer support cycles
2025-01-22 14:16:02 <@humaton:fedora.im> usinig UBI images and building everything? Usuing the sclog images linked in the issue?
2025-01-22 14:16:03 <@dkirwan:fedora.im> production grade
2025-01-22 14:16:29 <@humaton:fedora.im> that is not real answer
2025-01-22 14:16:43 <@humaton:fedora.im> We need to setup postgres cluster
2025-01-22 14:17:06 <@Zlopez:matrix.org> If the forgejo is not built for RHEL, it doesn't make much sense to use it
2025-01-22 14:17:30 <@Zlopez:matrix.org> Could we use existing postgres db we have in Fedora Infra?
2025-01-22 14:17:36 <@humaton:fedora.im> its a golang application it can be build on anything...
2025-01-22 14:17:36 <@t0xic0der:fedora.im> Or we'd have to put in extra effort to package em
2025-01-22 14:17:36 <@t0xic0der:fedora.im> These dependencies can be difficult to find in RHEL https://codeberg.org/fedora/oci-image-definitions/src/branch/main/forgejo/Dockerfile#L3
2025-01-22 14:17:55 <@t0xic0der:fedora.im> Which is prolly not going to be worth it - but I understand where David Kirwan is coming from 
2025-01-22 14:17:56 <@Zlopez:matrix.org> Or do we want to have separate postgres for Forgejo?
2025-01-22 14:18:27 <@humaton:fedora.im> clang and llvm are available in the appstream
2025-01-22 14:19:26 <@humaton:fedora.im> Yes we do want to have a postgres cluster deployed in openshift for forgejo
2025-01-22 14:19:37 <@humaton:fedora.im> 1 or 2 replication hosts
2025-01-22 14:19:55 <@t0xic0der:fedora.im> jednorozec: Is it worth exploring if RHEL can be used or are we sticking to Fedora base image?
2025-01-22 14:20:00 <@humaton:fedora.im> if you look at the help deployment I mentioned last week there  is a section about it
2025-01-22 14:20:29 <@Zlopez:matrix.org> I wasn't here last week, so I probably missed that
2025-01-22 14:21:08 <@t0xic0der:fedora.im> The notes were shared but I will forward those to you - No problems at all
2025-01-22 14:21:09 <@humaton:fedora.im> sure it is. If we have supported rhel image. But I think we will still need to put layers on top of it with our configuration os postgres
2025-01-22 14:21:41 <@t0xic0der:fedora.im> Oooh - natively installed Postgres? Not postgres on a different container? Interesting.
2025-01-22 14:21:42 <@Zlopez:matrix.org> I will find them somewhere in e-mail
2025-01-22 14:21:43 <@humaton:fedora.im> if you look at the helm deployment I mentioned last week there  is a section about it
2025-01-22 14:22:10 <@humaton:fedora.im> !link https://code.forgejo.org/forgejo-helm/forgejo-helm#configuration
2025-01-22 14:22:39 <@humaton:fedora.im> helm configuration referencing the deployment of code.forgejo.org
2025-01-22 14:23:28 <@humaton:fedora.im> this is the postgres configuration they are running https://github.com/bitnami/charts/tree/main/bitnami/postgresql-ha
2025-01-22 14:24:51 <@dkirwan:fedora.im> AWS RDS with a postgresql engine could be explored also ?
2025-01-22 14:25:32 <@Zlopez:matrix.org> I don't think we want to host this on AWS, but rather in our own infrastructure
2025-01-22 14:29:37 <@humaton:fedora.im> David Kirwan: well yes but I have problem that we are then exposed to cost of AWS if we would ever lose sponsorship from Amazon
2025-01-22 14:30:08 <@humaton:fedora.im> if we deploy it in openshift based on rhel9 the cost is the cost of operating the cluster
2025-01-22 14:31:11 <@humaton:fedora.im> there may already be replicated cluster template in openshift
2025-01-22 14:31:52 <@dkirwan:fedora.im> I'd imagine theres a few supported ways. might be an operator even
2025-01-22 14:32:39 <@humaton:fedora.im> we will need few more services
2025-01-22 14:32:53 <@humaton:fedora.im> so that os PostgreSQL, Redis, Opensearch
2025-01-22 14:33:39 <@humaton:fedora.im> we need to build from source on the Forgejo container image
2025-01-22 14:33:50 <@humaton:fedora.im> we need to build from source only the Forgejo container image
2025-01-22 14:34:28 <@humaton:fedora.im> so that is PostgreSQL, Redis, Opensearch
2025-01-22 14:36:46 <@humaton:fedora.im> but i think we should do something else first
2025-01-22 14:37:33 <@humaton:fedora.im> !topic Openshift app space
2025-01-22 14:37:37 <@humaton:fedora.im> !link https://pagure.io/fedora-infra/forgejo-deployment/issue/2
2025-01-22 14:38:03 <@humaton:fedora.im> we need someone to define the openshift app forgejo for staging and prod cluster
2025-01-22 14:38:50 <@humaton:fedora.im> and apply the changes so we can delegate access to the staging app to other people 
2025-01-22 14:40:28 <@gwmngilfen:fedora.im> i don't know enough yet to volunteer for that, but I'd like to follow along for sure
2025-01-22 14:40:53 <@lenkaseg:fedora.im> + 1, I'd like to follow along here too
2025-01-22 14:41:18 <@lenkaseg:fedora.im> //+1, I'd like to follow along here too
2025-01-22 14:41:35 <@gwmngilfen:fedora.im> (plus FOSDEM is going to occupy the next 2 weeks)
2025-01-22 14:42:55 <@gwmngilfen:fedora.im> i guess my shortcoming is knowledge of our openshift clusters, but I'd be happy to spin up minikube locally and at least test the helm chart - no idea if that's actually useful though?
2025-01-22 14:43:07 <@dkirwan:fedora.im> Are we planning to deploy via Helm?
2025-01-22 14:43:11 <@dkirwan:fedora.im> or we're not sure yet ?
2025-01-22 14:44:26 <@humaton:fedora.im> We discussed it last week on infra weekly, and Kevin had a good note. We should not be afraid to deploy new things and try different approaches
2025-01-22 14:44:30 <@amoloney:fedora.im> I would suggest using the !proposal or even !agreed to note the plan for deployment, even if its not fully agreed here today as it can be sent out post-meeting for wider feedback
2025-01-22 14:44:39 <@humaton:fedora.im> so I \think we should try to make the helm deployment happen
2025-01-22 14:45:09 <@humaton:fedora.im> Using helm means it can be running by the end of the week But with upstream as base images
2025-01-22 14:45:30 <@humaton:fedora.im> I dont care for staging and it even might be a good idea to do that
2025-01-22 14:45:39 <@dkirwan:fedora.im> So a minimal ansible playbook/role to launch helm...
2025-01-22 14:45:54 <@humaton:fedora.im> But we definately need a playbook https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps that will define the space for us
2025-01-22 14:46:35 <@dkirwan:fedora.im> We'll need helm configured and available on the os-control and os-control.stg machines then also
2025-01-22 14:46:44 <@humaton:fedora.im> yup, we can configure the heml by variables to some extend. Maybe if replacing its images with services based on openshift operators? 
2025-01-22 14:47:09 <@humaton:fedora.im> Does it require some extra work? 
2025-01-22 14:47:50 <@humaton:fedora.im> My idea was to fork the forgejo helm under fedora org and do some changes there if needed.
2025-01-22 14:47:52 <@dkirwan:fedora.im> Can be installed manually just to get running, but ideally it also needs to be added to the ansible role managing the os-control systems
2025-01-22 14:48:06 <@humaton:fedora.im> right
2025-01-22 14:48:24 <@dkirwan:fedora.im> might be easy as adding helm to the package install tasks vOv
2025-01-22 14:49:13 <@humaton:fedora.im> David Kirwan: so since you know what need to be done for helm to be available and for the openshift playbook to work. 
2025-01-22 14:49:41 <@humaton:fedora.im> can you create a Ticket for it under fedora-infra and link it in comment https://pagure.io/fedora-infra/forgejo-deployment/issue/2
2025-01-22 14:49:58 <@dkirwan:fedora.im> Yeah i can take that on, maybe lenkaseg and Gwmngilfen wants to join ? anyone else interested too of course
2025-01-22 14:50:10 <@lenkaseg:fedora.im> I'm in!
2025-01-22 14:50:12 <@gwmngilfen:fedora.im> i'll certianly follow along
2025-01-22 14:50:15 <@gwmngilfen:fedora.im> thanks!
2025-01-22 14:50:23 <@humaton:fedora.im> !agreed David will create tracking issue and ping interested parties 
2025-01-22 14:50:23 <@t0xic0der:fedora.im> Let me know how I can be of help as well
2025-01-22 14:50:51 <@humaton:fedora.im> hum
2025-01-22 14:50:57 <@humaton:fedora.im> we have 10 mins
2025-01-22 14:51:04 <@humaton:fedora.im> but we have progress!
2025-01-22 14:51:25 <@t0xic0der:fedora.im> Wanna talk about the Pagure Exporter port to Forgejo or should we keep it for the next meetings?
2025-01-22 14:51:55 <@humaton:fedora.im> !topic Q&A
2025-01-22 14:52:08 <@humaton:fedora.im> ok so exporter Akashdeep Dhar ?
2025-01-22 14:52:27 <@t0xic0der:fedora.im> If we have enough time - Or else, Q&A is fine
2025-01-22 14:52:47 <@humaton:fedora.im> Well the meeting has no structure set in stone
2025-01-22 14:52:49 <@humaton:fedora.im> but
2025-01-22 14:53:09 <@humaton:fedora.im> talking about exporter is interesting since we still dont have the service to import it into...
2025-01-22 14:53:17 <@t0xic0der:fedora.im> ;P
2025-01-22 14:53:39 <@t0xic0der:fedora.im> Very early ideation but folks can find the initiative proposal here 
2025-01-22 14:53:41 <@t0xic0der:fedora.im> !link https://pagure.io/cpe/initiatives-proposal/issue/32
2025-01-22 14:53:53 <@t0xic0der:fedora.im> Lets wait until we have some deployment ready before I hammer it with the exports
2025-01-22 14:54:00 <@t0xic0der:fedora.im> Fin
2025-01-22 14:54:46 <@amoloney:fedora.im> if you have a few mins, could someone summarise the intended plan for deployment please?
2025-01-22 14:54:55 <@amoloney:fedora.im> for the notes, wont someone please think of the notes :D
2025-01-22 14:57:04 <@t0xic0der:fedora.im> Not sure of the summary here but I can forward the meeting summary/logs to Discussion FPO thread to funnel people in
2025-01-22 14:57:17 <@t0xic0der:fedora.im> We can use all the visibility and assistance we can get
2025-01-22 14:58:10 <@amoloney:fedora.im> Ideally there would be a !proposal: Helm will be used as the deployment mechanism for Forgejo. We will use a base image from Fedora Rawhide and the managament of Helm will be configured through opeshift etc
2025-01-22 14:58:21 <@amoloney:fedora.im> I cant do this part, I dont have the technical fluency
2025-01-22 14:59:10 <@amoloney:fedora.im> but it would be helpful to have an intention stated for the meeting that 'this is what were doing' so if someone reads the logs and thinks of a way to help/do it better, they can engage with us to improve things
2025-01-22 15:00:08 <@humaton:fedora.im> I will put your feedback into the meeting template Aoife Moloney 
2025-01-22 15:00:18 <@humaton:fedora.im> so we have better structure next week
2025-01-22 15:00:40 <@humaton:fedora.im> and we are at the hour
2025-01-22 15:00:51 <@amoloney:fedora.im> thank you! Ive seen it done in other meetings and its very helpful to just jump straight to that outcome, and then re-read the conversation if needed
2025-01-22 15:00:56 <@humaton:fedora.im> !endmeeting