For a builder in the compose channel we need /mnt/koji mounted there and it should be done via sshfs. We chose buildvm-s390x-01.s390.fedoraproject.org as the builder that should have ssh access to a place where /mnt/koji can be mounted from, details would be in the etherpad created when setting up the firewall rules.
sshfs aka port 22/tcp from build-vm-s390x-01.s390.fedoraproject.org 10.16.0.11 to 10.5.125.61 (koji01) and 10.5.125.62 (koji02)
any update?
any update here? second mass rebuild also finished, so it would be really nice to start producing composes.
My last info is that @kevin plans to work on it yesterday/today.
@sharkcz great, thanks!
@puiterwijk set this up last night, so it should be good to go.
We both dislike this setup and will be trying to think of better ways to do this...
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks, I've asked for s390x composes in https://pagure.io/releng/issue/6954
In the s390 koji we used maxjobs=1 in kojid.conf of the compose builder, so the composes/runroots will run sequentially to lower the chance of congestion on the network. Shouldn't we do the same on buildvm-s390x-01?
That sounds like a good idea, yes.
Done. (set buildvm-s390x-01 to maxjobs = 1).
Login to comment on this ticket.