aarch64 vms for OSBS cluster #8442
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/fedora-infrastructure#8442
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?
Describe what you would like us to do:
Now that we have new hardware available for aarch64 would it be possible to provision the following
In Staging : 3 Virtual Machines ( 4 CPUS, 16GB RAM, 120GO LVM)
In Production : 3 Virtual Machines ( 4 CPUS, 16GB RAM, 120GO LVM)
The following networking setup also needs to be done :
osbs-control01(.stg).phx2.fp.o needs to have ssh access to the aarch64 VMs in order to run ansible from it.
Both clusters x86_64 and aarch64 are talking to each others using REST API on the port 8443, this port needs to be open
osbs-master01.(stg.)phx2.fedoraproject.org needs to be able to communicate with osbs-aarch64-master01.(stg.)arm.fedoraproject.org, osbs-aarch64-node01.(stg.)arm.fedoraproject.org, osbs-aarch64-node02.(stg.)arm.fedoraproject.org on port 8443.
When do you need this to be done by? (YYYY/MM/DD)
When possible :-)
Metadata Update from @cverna:
I will be doing the following:
rename vmhost-aarch64-17 to vmhost-a64-osbs-01
change the vlans on this host to being br0 on .125 and br1 on .128
turn off old hosts in moonshot
build out new hosts on emag
turn over to cverna
Metadata Update from @smooge:
Also: vm's will be moved to be on the .125 / .129 networks too so they avoid the RHIT firewall between subnets.
Note that we might have to adjust the iptables firewalls on machines tho.
Hardware has been set up and initial kickstarts and variables have been made. Talked with @cverna that items were met. Will close ticke.t
Metadata Update from @smooge: