redeploy aws proxies #12469
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 or 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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/fedora-infrastructure#12469
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 number of proxies in aws:
Many/most of these are c5d.xlarge, but thats an older type. Thats 8GB memory and 4 cpus and it's not handling things too well these days.
So, we need to:
Find a better instance type. I think at least 16GB/8 cpus, but perhaps there's a better mix. We also want to make sure and have one disk with ~100GB of space.
Once we decide that, we need to take one out of dns and setup downtime in nagios one instance (probibly starting with proxy35 as it's been having the most problem lately)
Spin up the new one, add to dns, ansiblize.
We are entering final freeze, so we would need a freeze break to do these, but I think we can do so carefully, so we will need to request a freeze break...
@phsmoura was gonna work on this.
Metadata Update from @zlopez:
I was reviewing AWS instance types, and the c5d.2xlarge stands out for having similar specifications. It offers 8 CPUs, 16 GiB of memory, and 200 GB of SSD storage. Some proxies are already utilizing it
Looks like proxy09 is a c5n.2xlarge... thats the same cpus and disk, but 20GiB memory?
Perhaps one will work? Thats used by:
proxy09.fedoraproject.org: "ansible_product_name": "c5n.2xlarge",
proxy30.fedoraproject.org: "ansible_product_name": "c5n.2xlarge",
proxy31.fedoraproject.org: "ansible_product_name": "c5n.2xlarge",
proxy32.fedoraproject.org: "ansible_product_name": "c5n.2xlarge",
proxy38.fedoraproject.org: "ansible_product_name": "c5n.2xlarge",
proxy40.fedoraproject.org: "ansible_product_name": "c5n.2xlarge",
These are the ones that probibly we want to replace:
proxy33.fedoraproject.org: "ansible_product_name": "c5d.xlarge",
proxy34.fedoraproject.org: "ansible_product_name": "c5.2xlarge",
proxy35.fedoraproject.org: "ansible_product_name": "c5d.xlarge",
proxy36.fedoraproject.org: "ansible_product_name": "c5d.xlarge",
proxy37.fedoraproject.org: "ansible_product_name": "c5d.xlarge",
proxy39.fedoraproject.org: "ansible_product_name": "c5d.xlarge",
Thoughts?
done so far: proxy 35, 36 and 37