Deploy Siguldry to the staging environment #13199
Labels
No labels
announcement
anubis
authentication
aws
backlog
blocked
bodhi
ci
cloud
communishift
copr
database
day-to-day
dc-move
deprecated
dev
discourse
dns
downloads
easyfix
epel
firmitas
forgejo_migration
Gain
High
Gain
Low
Gain
Medium
gitlab
greenwave
hardware
help wanted
high-trouble
koji
koschei
lists
low-trouble
medium-trouble
mirrorlists
monitoring
Needs investigation
odcs
OpenShift
ops
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
release-monitoring
releng
request-for-resources
s390x
security
SMTP
sprint-0
sprint-1
src.fp.o
staging
unfreeze
waiverdb
websites-general
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
infra/tickets#13199
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?
Description of request
I anticipate that the server parts of the new signing service will be ready for a staging deployment starting the week of the 23th. There is some packaging work to do which I believe I'll be able to take care of next week.
The requirements are similar to Sigul in that there's an isolated server host, a bridge host, and then clients including one that runs robosignatory.
The server and bridge should be RHEL 10. I'll work on Ansible roles, but will definitely need some detailed review/hand-holding for them. The client should be Fedora. To properly test the client with rpm signing, it'll need to have a version of rpm that includes https://github.com/rpm-software-management/rpm/pull/4125 so we'll need to consider how best to do that.
I'll help get this rolled out in the next sprint...
Or perhaps the one after. ;)
Just to update here, I'm working on getting builds for EPEL 10.
We need https://bugzilla.redhat.com/show_bug.cgi?id=2455556 done, and there's also rust-cryptoki and (for tests/staging environment HSM) kryoptic. I've asked Jakub and Simo about those.
I've also started on some ansible for it, but it's very much not done and there's a lot of copy/pasting that maybe we don't need.
There's now a build for EPEL 10: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-04073d0191
Okay, one last update. I subsequently realized there's a lot of EPEL 10 branches and the above is only for 10.3.
I've rebuilt it all for 10.2, but doing it for 10.1 is a bit more of a challenge because there's an old version of bindgen in epel10.1. I know EL 10.2 is "soon" so it possibly won't matter when we get to it, but we start on this before 10.2 is available, we can probably also just use the 10.2 RPMs and I suspect they'll work, unless there's some big glibc breaking changes that happened.
I'm also working on admin documentation - source is here - which might be helpful when looking over the horrible ansible I'm about to write. I'm filling it in as I go so there's lots of gaps, but definitely file issues for any sections of the docs that don't make sense, need expanding, etc.
Just FYI, I will be out on pto all next week... but can help with merging/deploying after I get back.
Yup, no worries. Enjoy your vacation and think nothing of signing.