Adjust playbooks/manual/staging-sync/templates/koji-reset-staging.sql script for phx2->iad2 koji migration #8960
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
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/fedora-infrastructure#8960
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?
We have a script we use when migrating the prod -> stg koji database.
We should adjust this to use for the phx2->iad2 move.
playbooks/manual/staging-sync/templates/koji-reset-staging.sql is the script.
We want to refer to iad2.fedoraproject.org in places where it mentions stg.phx2.fedoraproject.org
Builders will be created new, so we don't need to do that.
We may want to look at the dump and see if there's any other (non historical) places we want to adjust. Possibly more krb5 credentials?
Metadata Update from @smooge:
I had a quick look over the sql file mentioned.
Is this going to be a staging instance in IAD2? If not there is some stuff in there to add users for staging only that may need to be adjusted as well. The only mention of phx2 is in relation to krb principals for certain users.
There will be but not at first.
I wonder if it wouldn't make sense to duplicate this script just for the migration phx2 -> iad2 as we will likely still need it to do prod -> stg in iad2 once we rebuild stg.
If the iad2 koji deployment is going to be fresh do we need this script?
The script mostly just prepares a running db for a dump by the look of it so if the db is a fresh install and there are no builders or jobs running it could be just a case of dump it in?
Or will this have to be run a number of times on a 'live' koji instance?
The iad2 instance will be a migration of our current existing PROD koji database.
Yes, we should make a seperate script that only does those things we need for this, we definitely to not want to do everything that staging script does.
We do want to:
We could add new iad2 builders here, or just add them from command line since it's a one time thing
and I guess thats it. :)
I have created a PR based on the comments from Kevin. I have made some best guesses about the db so this will probably need to be adjusted slightly but its a start
https://pagure.io/fedora-infra/ansible/pull-request/109
Merged! thanks!
Metadata Update from @kevin: