#meeting:fedoraproject.org log

<@nirik:matrix.scrye.com>

15:00:20

!startmeeting riscv-sig

<@meetbot:fedora.im>

15:00:22

Meeting started at 2025-04-29 15:00:20 UTC

<@meetbot:fedora.im>

15:00:22

The Meeting name is 'riscv-sig'

<@nirik:matrix.scrye.com>

15:00:49

hey everyone, I'm in another meeting, so only sort of here, but can try...

<@davidlt:matrix.org>

15:01:00

!hi

<@zodbot:fedora.im>

15:01:03

David Abdurachmanov (davidlt)

<@rwmj:matrix.org>

15:01:37

hello

<@nhanlon:beeper.com>

15:01:38

!hi

<@kashyapc:fedora.im>

15:02:01

!hi

<@zodbot:fedora.im>

15:02:13

Kashyap Chamarthy (kashyapc)

<@abologna:matrix.org>

15:02:16

!hi

<@zodbot:fedora.im>

15:02:24

None (abologna)

<@kashyapc:fedora.im>

15:02:24

(I'm in a parallel meeting; so half-present here, afraid)

<@nhanlon:beeper.com>

15:03:04

me x 2 😃

<@abologna:matrix.org>

15:03:19

so, let's start by discussing the move to that new koji server? sounds good?

<@kashyapc:fedora.im>

15:03:32

Sure

<@abologna:matrix.org>

15:04:11

alright

<@abologna:matrix.org>

15:04:17

!topic new koji server

<@abologna:matrix.org>

15:05:13

the machine has been up for a while, we've been basically putting off using it because we were all super busy making F42 happen, but now that that's out of the door I think we should focus on making it happen

<@rwmj:matrix.org>

15:05:37

is the plan to move existing builders across to it?

<@abologna:matrix.org>

15:05:48

yes

<@davidlt:matrix.org>

15:05:49

I still have no instructions how to reach keytab for a machine.

<@davidlt:matrix.org>

15:06:01

Thus I haven't looked into instructions.

<@nirik:matrix.scrye.com>

15:06:10

They are on the hub...

<@rwmj:matrix.org>

15:06:29

I'd also like to retire `nufive` and `nujive` (both are SiFive Unmatched boards)

<@nirik:matrix.scrye.com>

15:06:33

I can get the dir. I think I only did one or two so far, but I can expand that

<@davidlt:matrix.org>

15:07:19

I understand that they are on the hub, but how do I connect to it to reach them? 😄

<@nirik:matrix.scrye.com>

15:08:46

https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/sshaccess/

<@nirik:matrix.scrye.com>

15:09:02

and then ssh to riscv-koji01.iad2.fedoraproject.org

<@emma:rory.gay>

15:10:19

👀

<@nirik:matrix.scrye.com>

15:10:20

I can help debug with anyone that has access to get in

<@abologna:matrix.org>

15:11:11

so this is needed to... generate keytabs and hand them over to people with boards?

<@abologna:matrix.org>

15:11:29

I'm very unfamiliar with the whole process, so probably a silly question

<@nirik:matrix.scrye.com>

15:11:48

the keytabs are already generated. They need to be distributed to those hosts... and the host has to have a local hostname matching the keytab.

<@abologna:matrix.org>

15:12:13

so there is 1:1 relationship between keytabs and builders, right?

<@rwmj:matrix.org>

15:12:28

it doesn't have to be a public hostname, right?

<@abologna:matrix.org>

15:12:42

Richard Jones: AFAIK that's not needed

<@nirik:matrix.scrye.com>

15:12:43

yes and yes

<@rwmj:matrix.org>

15:12:44

on fedora.riscv.rocks we have hostnames but they are not resolvable publicly

<@nirik:matrix.scrye.com>

15:12:55

right, the hostname just has to be local

<@nirik:matrix.scrye.com>

15:13:07

koji checks/uses that. dns/external it can be anything you like

<@abologna:matrix.org>

15:13:54

so to be clear, you have generated a number of keytabs (how many?) and they are ready to be handed over to the people running builders

<@emma:rory.gay>

15:13:57

im not in the meeting, but does dotnet work on riscv? 👀

<@emma:rory.gay>

15:13:57

if so, i'd be interested in signing up so i can test my own stuff under RV

<@davidlt:matrix.org>

15:14:42

IIRC the keytab is generated once a hostname is added.

<@davidlt:matrix.org>

15:14:52

Those are available on the hub.

<@nirik:matrix.scrye.com>

15:15:17

I need to look. pretty distracted right now

<@abologna:matrix.org>

15:15:46

Emma [it/its]: https://fedoraproject.org/wiki/Architectures/RISC-V is a good starting point, no idea about .NET specifically, but you can come hang out in https://matrix.to/#/#riscv:fedoraproject.org later and we can help you figure that out :)

<@rwmj:matrix.org>

15:16:10

these all say "no builds" http://fedora.riscv.rocks/koji/search?match=glob&type=package&terms=dotnet* so I guess not

<@emma:rory.gay>

15:16:24

or theyre excluded form the build system

<@davidlt:matrix.org>

15:16:24

dotnet has gained some support, and to my understand the latest version should build (but we didn't try it).

<@davidlt:matrix.org>

15:16:34

Officially it's not supported, and bits might be missing.

<@abologna:matrix.org>

15:16:42

on https://riscv-koji.fedoraproject.org/koji/hosts I see just one riscv64 host defined. maybe a single one was created for testing purposes, and more need to be added?

<@emma:rory.gay>

15:16:46

no builds but is marked as included

<@davidlt:matrix.org>

15:17:07

Yes, we haven't tried to enable it, but to my recent discussions with some folks it should build.

<@nirik:matrix.scrye.com>

15:17:23

abologna: quite possible. I did that work about a month ago... :)

<@abologna:matrix.org>

15:17:35

Emma [it/its]: I will kindly ask you not to derail this planning meeting... please come hang out in the channel later ;)

<@emma:rory.gay>

15:17:49

my bad, sorry! :)

<@abologna:matrix.org>

15:18:02

no worries whatsoever :)

<@abologna:matrix.org>

15:18:35

so davidlt if at least one keytab exists you should be able to look into connecting a builder to the new koji instance, right?

<@davidlt:matrix.org>

15:18:52

Once, I figure out how to connect to it.

<@nirik:matrix.scrye.com>

15:19:00

I connected mine as a test.

<@nirik:matrix.scrye.com>

15:19:11

but I can make more keytabs for sure, or you could use that one for testing.

<@davidlt:matrix.org>

15:19:18

I am trying to that in parallel, but failing so far.

<@abologna:matrix.org>

15:20:41

maybe save it for later. the important think IMO is that we know you have what you need for testing. I'm sure nirik will be happy to answer questions after the meeting

<@nirik:matrix.scrye.com>

15:21:11

yep. happy to

<@abologna:matrix.org>

15:21:43

if you manage to connect a builder, we can try kicking off a build for some package that doesn't require patched source

<@abologna:matrix.org>

15:21:51

the plan was to import all of F42 as-is, right?

<@abologna:matrix.org>

15:22:12

IIRC davidlt was saying that rebuilding from scratch would be too much work and not worth it

<@davidlt:matrix.org>

15:22:33

Yes, it would be an import F42 as-is as a starting point.

<@nirik:matrix.scrye.com>

15:22:41

we can't do any builds until we import a buildroot

<@davidlt:matrix.org>

15:23:00

From "scratch" I would assume re-bootstrap, but that would be a month-long journey with no benefit.

<@davidlt:matrix.org>

15:23:19

We cannot do any builds before builders are connected too 😄

<@abologna:matrix.org>

15:23:35

I was remembering correctly then. I trust your judgement, if you say we shouldn't do it then we won't

<@davidlt:matrix.org>

15:23:37

1st builders, then import F42 package set into a new Koji.

<@abologna:matrix.org>

15:24:27

when we import old contents we should take the opportunity to clear out old garbage if any exists

<@nirik:matrix.scrye.com>

15:24:28

sure... we could import now, but yeah, we need some builders to do anything

<@abologna:matrix.org>

15:24:35

e.g. packages that have been retired from Fedora

<@abologna:matrix.org>

15:25:48

yeah, definitely we want to delay the import until later, otherwise we risk having to re-sync some of the stuff. let's figure out how to get builders connected first

<@rwmj:matrix.org>

15:26:08

are they a problem? can't they just be ignored?

<@davidlt:matrix.org>

15:26:45

We are ignoring them, and I am trimming them at random time (usually before starting a new Fedora cycle).

<@abologna:matrix.org>

15:27:05

well it's our opportunity to do some spring cleaning, I think we should take it

<@abologna:matrix.org>

15:27:21

start fresh

<@abologna:matrix.org>

15:28:12

anyway I think we have a good sense of what needs to happen to move things forward

<@abologna:matrix.org>

15:28:43

I'd say let's move on

<@nirik:matrix.scrye.com>

15:29:34

is there a builder image/config ? or we need to finish that too....

<@abologna:matrix.org>

15:30:14

well we certainly want the builders to be running F42

<@abologna:matrix.org>

15:30:24

no idea about the config

<@abologna:matrix.org>

15:30:35

davidlt wanted to have ready-to-deploy images I think?

<@abologna:matrix.org>

15:31:17

I can definitely work on building those but I would need to know what packages need to be included and what the configuration for kojid should look like

<@davidlt:matrix.org>

15:31:17

We don't really need those images as long as we have instructions. Instructions (current) are kinda short, but we could make a disk image with all in.

<@davidlt:matrix.org>

15:31:47

That would safe a bit of time setting up all the boards.

<@abologna:matrix.org>

15:32:23

I'm fine either way. if the instructions are straightforward to follow, we can leave it at that. but cooking ready to deploy VF2/P550/Megrez images would be feasible too

<@nirik:matrix.scrye.com>

15:32:25

yeah, it should just be packages + kojid config

<@abologna:matrix.org>

15:33:36

or we could have a "riscv-koji-builder" RPM that pulls in all dependencies and installs the correct configuration too

<@abologna:matrix.org>

15:33:56

IIUC you're still going to need to connect to each builder at least once, to install the keytab

<@davidlt:matrix.org>

15:34:10

No need for any meta RPM, I think.

<@abologna:matrix.org>

15:34:36

in any case the first steps are 1) figure out a working kojid configuration and 2) document it

<@davidlt:matrix.org>

15:35:37

That I have, I think. I already use updated stuff from Ansible.

<@nirik:matrix.scrye.com>

15:36:12

yeah, it should be pretty easy to copy one from there and adjust...

<@abologna:matrix.org>

15:36:28

I think so too, just needs to be validated

<@kashyapc:fedora.im>

15:37:20

Is there an example of this `kojid` config somewhere?

<@davidlt:matrix.org>

15:39:19

Yes, full config is available in Fedora Infra ansible repo.

<@davidlt:matrix.org>

15:39:36

I am using it from there, just deleted all non-relevant parts.

<@nirik:matrix.scrye.com>

15:39:52

https://pagure.io/fedora-infra/ansible/blob/main/f/roles/koji_builder/templates/kojid.conf

<@kashyapc:fedora.im>

15:39:59

Thanks! Idon't need it myself; I was just curious

<@davidlt:matrix.org>

15:40:56

nirik: just to make sure, I do have an account to SSH into the riscv-koji01.iad2.fedoraproject.org ?

<@nirik:matrix.scrye.com>

15:41:21

yes, your fedora account system account should be added there...

<@nirik:matrix.scrye.com>

15:41:31

if it's not working, will need to look at logs...

<@kashyapc:fedora.im>

15:42:53

Thanks! I don't need it myself; I was just curious

<@davidlt:matrix.org>

15:43:05

I can ssh into secondary01.fedoraproject.org, but non in any other hosts listed on wiki or riscv-koji01.iad2.fedoraproject.org.

<@nirik:matrix.scrye.com>

15:43:34

hum, ok, can look after the meeting?

<@davidlt:matrix.org>

15:43:36

This is probably one of those situations there it's better to look at in the morning 😄

<@nirik:matrix.scrye.com>

15:45:37

ok, ping me back in the channel, perhaps with a pastebin of -vvvv ssh to it?

<@davidlt:matrix.org>

15:48:23

nirik: any news about the registry?

<@nirik:matrix.scrye.com>

15:50:11

I have a todo item to generate a bot account and token.

<@nirik:matrix.scrye.com>

15:50:22

I guess I can put it on the hub also so folks that need it can get it?

<@nirik:matrix.scrye.com>

15:50:33

I was going to tie it to the fedora-testing repo...

<@nirik:matrix.scrye.com>

15:52:18

https://quay.io/organization/fedora-testing

<@abologna:matrix.org>

15:53:39

I have to drop off, period :)

<@kashyapc:fedora.im>

15:53:56

Then, please end the meeting here :)

<@kashyapc:fedora.im>

15:54:06

Otherwise, we might leave it "dangling"

<@davidlt:matrix.org>

15:54:47

!endmeeting