Review / refresh the "request for resources" process #13288
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
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
infra/tickets#13288
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
In relation to the Hummingbird discussion on devel@ , I found the wiki page on creating a SIG, which is fairly modern and relevant, great. I updated it a bit, no big deal.
However, it links to an infrastructure Request for Resources page, which read like a portal to 2009 or so.
I've updated it a little, but it could probably do with a thorough rewrite by someone more infra-y than me, and/or being killed with fire. I sort of invented a distinction between "routine" and more complex requests, purely so it looks less scary to anyone encountering it from the SIG creation page (and especially the hummingbird folks); please check this over.
I can't find any more modern replacement for it. I don't see anything in infra docs. I don't see any more modern infra wiki page. AFAICT, this is still at least notionally the 'current' doc and process for anyone who wants to 'request resources' from infra. Aside from the bits I just invented, I can't really find anything to cover more routine requests like "we want an org in Forge", "we want a tag in Discussion", stuff like that, which doesn't make them sound terrifying. I guess it's Common Sense(tm) to just file a ticket and ask, but...
There is an accompanying SOP. The Wiki page links to https://fedoraproject.org/wiki/Request_for_resources_SOP , which points you to https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/requestforresources.html , which does not exist. It seems like the page actually exists at https://docs.fedoraproject.org/en-US/infra/sysadmin_sops/requestforresources/ , which doesn't appear to be discoverable from the side bar, you can only find it by searching. I don't know if anyone's looked at or followed it for years.
I think we should discuss this at the weekly meeting thursday... and perhaps have a discussion thread on it.
IMHO we should possibly move this process to be much more openshift centric, but I guess there's still cases where thats not going to work. Will ponder on it.
Oh, minor update, I later thought better of the routine/non-routine distinction and tweaked it again to just say "this process doesn't cover routine requests, for those, file an ad hoc ticket".