-
Notifications
You must be signed in to change notification settings - Fork 12
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
aarch64 machine access for exprimenting Fedora CoreOS #110
Comments
Invitation sent! thanks Ed |
Thanks Ed! |
This is the sort of collaboration I like seeing. 👍 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is running, so we can close it. |
Noted at coreos/fedora-coreos-tracker#69 - reopening this to track that issue. Also: conversation with @sinnykumari about adding more members to project. |
Hi Ed, Please add FCOS community members with email address [email protected], [email protected] and [email protected] to Fedora CoreOS project Thanks |
and one more: [email protected] |
Those four folks have been invited! |
Thanks @edolnx |
If you are interested in filing a request for access to the Works on Arm test and
CI infrastructure, please fill out the details below, or contact Ed Vielmetti at [email protected] with questions.
If you are just making a comment, ignore/delete those fields and file your issue.
Name, email, company, job title
Sinny Kumari, [email protected], Red Hat, Senior Software Engineer
Note: I should be able to give access to this machine to Fedora CoreOS community members whoever needs it to test or debug Fedora CoreOS related work.
Note that projects with two or more participants are preferred.
Project Title and description
Fedora CoreOS initial support work on aarch64
Which members of the community would benefit from your work?
Fedora CoreOS
Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?
Yes, Fedora CoreOS is in early design phase and related discussion occurs at https://github.com/coreos/fedora-coreos-tracker. Content of Fedora CoreOS will be built from Fedora packages which are available at http://koji.fedoraproject.org/koji/
What infrastructure (computing resources and network access) do you need? (see: https://www.packet.net/bare-metal/)?
Decent memory and CPU with nested virt capability
According to https://www.packet.net/cloud/servers/ , armv8 comes only with c1.large.arm . This should be good enough for us.
Let us know if you need short-term (one time) support, or if this is a request for
continuous ongoing support. If possible, please identify foundations or other
support organizations that can help with long-running projects.
Continuous ongoing effort
Building Fedora CoreOS is going to be a continuous effort at least till we do our first Fedora CoreOS release. Community members will need access to aarch64 machine for things like test, debug and fix aarch64 related issues.
Describe the continuous integration (CI) system in use or desired for this project.
Not at the moment
Please state your contributions to the open source community and any other relevant initiatives
I am involved with Fedora Atomic Host and worked in past on enabling Fedora Atomic Host on aarch64 and ppc64le. Also, I help in getting Fedora Atomic Two Week release out for all supported architectures(x86_64, ppc64le, aarch64)
I am also involved in Fedora CoreOS which will be successor of Fedora Atomic Host once released and work towards getting it's first release officially available.
Brag a little bit about yourself, please!
The text was updated successfully, but these errors were encountered: