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.
Metadata Update from @cverna: - Issue tagged with: OSBS, request-for-resources
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: - Issue assigned to smooge - Issue priority set to: Waiting on Assignee (was: Needs Review)
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: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.