Describe what you need us to do: Enable aarch64 to AWS. @smooge has deployed autocloud-backend-aarch64.arm.fedoraproject.org so the core HW bits should be in place. The cloud images as of today have 100% bits required (kernel-4.19.4-300.fc29) stable so the next cloud images are AWS aarch64 ready.
When do you need this? (YYYY/MM/DD) ASAP
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact?
Metadata Update from @pbrobinson: - Issue assigned to sayanchowdhury
+1 to ASAP nature of this. Please treat as an emergency.
I don't quite understand the ASAP nature of this. This is the first I've heard of aarch64 AWS.
We are working on moving our upload to AWS code to use the plume/ore tools from the mantle codebase. If there is a lot of work to be done I don't really see a lot of value in investing in fedimg at this time. @sayanchowdhury would be able to give the best educated answer on this.
I see another ticket has been opened against the cloud sig (i'm progressing through my notification emails): https://pagure.io/cloud-sig/issue/293
There is a PR against fedimg for this: https://github.com/fedora-infra/fedimg/pull/156
So, this is all live and announced now.
Metadata Update from @puiterwijk: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.