Since our arm hardware at RDU2 is still off line and will be likely for a while, lets spin up a instance in aws for maintainers to test with.
Perhaps @mobrien could do this.
Metadata Update from @mobrien: - Issue assigned to mobrien
Metadata Update from @mobrien: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble
I have put up an instance aarch64-test01.fedorainfracloud.org in AWS with f33. Some follow up questions
aarch64-test01.fedorainfracloud.org
We used to have 2 of these, will I put up another?
Do we see this staying in AWS or going to RDU2 when infra becomes available? I could clean up a few lines in Ansible if it's staying in AWS.
Is it ok to just have f33 or do we need other versions?
Metadata Update from @mobrien: - Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)
1 is probibly fine for now.
I think we will move back to rdu2 once we have that hardware on. It would then be identical to the hardware in the build system.
I think just f33 is fine, people can use mock chroots for other things. ;)
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks Kevin, I'll update the wiki now and close
Login to comment on this ticket.