Skip to content
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

Add emerging platforms process/flow #1569

Closed
travier opened this issue Sep 7, 2023 · 3 comments
Closed

Add emerging platforms process/flow #1569

travier opened this issue Sep 7, 2023 · 3 comments

Comments

@travier
Copy link
Member

travier commented Sep 7, 2023

Describe the enhancement

Add a lighter process to add a new supported platform for Fedora CoreOS.

The idea is that for lightly supported platforms we do the Ignition and Afterburn integration work and we stop there. Notably we do not produce disk images.

We then document a procedure to take one of our exiting image and tweak it to get a valid disk image for the new platform.

This would significantly reduce the overhead of adding new platform to Fedora CoreOS while keeping it reasonably low effort for users to setup FCOS on their favorite platform.

See PR for this process in #1562

System details

N/A

Additional information

Previous discussion in #719

@travier
Copy link
Member Author

travier commented Sep 7, 2023

Platforms that are candidate for this process:

Basically any platform already supported by cloud-init could be considered (https://github.com/canonical/cloud-init/tree/main/cloudinit/sources.).

@jlebon
Copy link
Member

jlebon commented Sep 13, 2023

We discussed this in today's community meeting:

AGREED: We generally like the idea of "emerging" platforms. We will continue fleshing out the UX and communications part of it in the ticket. (jlebon, 17:05:29)

@jlebon jlebon removed the meeting topics for meetings label Sep 13, 2023
@travier travier changed the title Add "lightly" supported platforms Add emerging platforms process/flow Oct 4, 2023
@travier
Copy link
Member Author

travier commented Oct 4, 2023

We now have this flow as of #1562. We'll keep iterating and I'll close this one as it does not need immediate action.

@travier travier closed this as completed Oct 4, 2023
@jlebon jlebon mentioned this issue Jan 18, 2024
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants