Set up maintainer test machine for s390x #11122
Labels
No labels
announcement
authentication
automate
aws
backlog
blocked
bodhi
ci
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Initiative Worthy
Closed As
Insufficient data
Closed As
Invalid
Closed As
Spam
Closed As
Upstream
Closed As/Will Not
Can Not fix
cloud
communishift
copr
database
deprecated
dev
discourse
dns
downloads
easyfix
epel
factory2
firmitas
gitlab
greenwave
hardware
help wanted
high-gain
high-trouble
iad2
koji
koschei
lists
low-gain
low-trouble
mbs
medium-gain
medium-trouble
mini-initiative
mirrorlists
monitoring
Needs investigation
notifier
odcs
OpenShift
ops
OSBS
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
rdu-cc
release-monitoring
releng
repoSpanner
request-for-resources
s390x
security
SMTP
src.fp.o
staging
taiga
unfreeze
waiverdb
websites-general
wiki
No milestone
No project
No assignees
7 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/fedora-infrastructure#11122
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
NOTE
If your issue is for security or deals with sensitive info please
mark it as private using the checkbox below.
Describe what you would like us to do:
Would it be possible to spin up an s390x maintainer test machine on IBM Cloud or elsewhere? @kevin also mentioned that @sharkcz might also be able to help with this. s390x is not exactly an accessible architecture.
This has been on my radar for quite some time, but we might be able to get an official test machine. Until then I can provide access to existing systems/VMs.
Do we want to keep this ticket here to track this?
Or should we just let @sharkcz work on it and let us know when it's ready? :)
@kevin, I think keeping the ticket open to track this is a good idea, but I'll leave it up to y'all to decide how to manage your issue tracker ;).
Metadata Update from @zlopez:
I'd like to jump in as officially we'd like also to investigate that even just for official CentOS SIGs builds on https://cbs.centos.org koji instance.
Is that possible to get access to s390x infra ?
@sharkcz How does it looks with the testing machine?
@sharkcz How does it looks with the testing machine?
@sharkcz @arrfab are there any updates to this ticket that need to be reflected?
@pcreech17 I'd like myself who to ping to get access to some s390x VMs so I'm at the "requester" side, like you , on this ticket ;-)
We have the
2352969 - ZCommunity3
account for the Fedora Copr purposes, where we have formally granted to start up to 18 machines for building in Fedora Copr. I'd be happy to start a VM there if we have a formal ACK from IBM folks who sponsor this.[backlog_refinement]
@praiskup Were you able to find somebody from IBM who can allow the requester to get a test VM?
Any news here? Should we still keep this open?
I would let it open. There is a project running for having a whole mainframe set up and available for the OpenMainframe project (part of Linux Foundation) and I am planning to use those resources for the additional VM as we (Fedora) are participating there in the Linux Working Group.
Awesome. Thanks!
another CentOS SIG recently asked (on irc) about s390x support for centos koji (cbs.centos.org) so , as Copr got access to resources, can I ask what's the process to even just have one VM for centos SIGs ?
@sharkcz Any update on this one?