-
-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support aarch64 on Fedora CoreOS baremetal like in AWS #1045
Comments
I haven't found reasonably priced (but serious, no rpi) arm64 hardware I'd like to add to my colo, and don't ship things I can't personally attest to. So it's out of scope for now. |
The honeycomb's seem like an appealing option though it seems like a large amount of cores for a cluster. RPI's can actually be viable with the help of https://github.com/pftf/RPi4 Fedora CoreOS maintainers have confirmed it running on RPI 4. |
Perhaps I'll find a suitable addition or find a hardware vendor sponsor in future. I wouldn't deploy RPI's there. Lack of remote management, fiddling with firmware, network booting, and the lack of resources for running anything meaningful, I think most would agree they're not for datacenter or lab use, more for hobbies (fun if you have the time, not knocking it). |
Honeycomb's look interesting. Not sure I follow the too many cores for a cluster comment. Maybe we have different experiences, but 16 cores is a modest little node. |
Considering stable streams have began shipping in Fedora CoreOS it would be nice to see typhoon setup CoreOS baremetal like it does for AWS. Considering the logic exists within AWS for Fedora CoreOS this should be somewhat simple to add.
Shortlist of items (I think) that would need to be addressed:
I would be happy to help with this effort in the maintainers are insterested in it.
The text was updated successfully, but these errors were encountered: