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

Clean up multi-arch support #1164

Closed
bgilbert opened this issue Nov 7, 2018 · 3 comments
Closed

Clean up multi-arch support #1164

bgilbert opened this issue Nov 7, 2018 · 3 comments

Comments

@bgilbert
Copy link
Contributor

bgilbert commented Nov 7, 2018

We currently wrap the architecture name into a board for historical reasons, and sometimes we treat it as a per-platform option. Cleanups are needed.

@bgilbert
Copy link
Contributor Author

bgilbert commented Nov 7, 2018

See coreos/mantle#940 (comment).

@arithx
Copy link
Contributor

arithx commented Feb 12, 2019

Here's some goals I'd like to see as an outcome of this refactor:

  • Change current terminology from CL specific board to architecture; update code that requires board to fetch the CL version of a given architecture
  • Utilize distribution flag when gating architectures during run-time
  • Add flag to build script to either allow a specified list of architectures to build (defaulting to all supported) or specify the distribution mantle is being built for (so that CL won't try to build architectures it doesn't/can't support)
  • Remove architecture from kola/ore platform-specific options in favor of a generic option
  • Store the architecture in the Flight object, change kola runner references to architecture to fetch from the Flight

@cgwalters cgwalters transferred this issue from coreos/mantle Feb 27, 2020
jcajka pushed a commit to jcajka/coreos-assembler that referenced this issue Mar 24, 2020
qemu: Silence errors from swtpm by default
@dustymabe
Copy link
Member

We've had some cleanups around this but don't have anything specific planned further. We'll close this and open PRs as new ideas come up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants