You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this feature request related to a problem? If so, please describe it.
Currently, architectures that are not x86_64 or aarch64 are considered an "external" architecture from peridot, and thus require additional effort to be part of the build system environment. Though this is the case, there are situations where this causes issues:
Kernels on the systems are different than the main architectures (x86/arm)
Builds may have failures in this manner that is easily solved by running on a normal EL system running mock (no kube or containers)
There may also be situations in the future too where having designated hosts for specific builds (such as kernel/grub2/others only for secure boot signing) would be ideal.
It may also be ideal to have something like KubeVirt support, which would eliminate having a mix of architectures that are either native or external.
Describe the solution you'd like to see
There should be options, whether in a peridot config or in the project itself, that assigns specific hosts to an architecture and allowing the selection of using "static hosts" if applicable or available for all architectures. For peridot configs, there could potentially be an option to send specific packages to some host too, but might be better within the UI.
Peridot should also be deployable to allow KubeVirt instead of managing pods itself.
Have you considered alternative solutions/features? If so, please describe them.
No response
Version and Build Information
Current
Additional Context
No response
The text was updated successfully, but these errors were encountered:
nazunalika
changed the title
[RFE] Allow for static builders and build host designations
[RFE] Allow for static builders and build host designations / KubeVirt support
Oct 30, 2022
Is this feature request related to a problem? If so, please describe it.
Currently, architectures that are not x86_64 or aarch64 are considered an "external" architecture from peridot, and thus require additional effort to be part of the build system environment. Though this is the case, there are situations where this causes issues:
There may also be situations in the future too where having designated hosts for specific builds (such as kernel/grub2/others only for secure boot signing) would be ideal.
It may also be ideal to have something like KubeVirt support, which would eliminate having a mix of architectures that are either native or external.
Describe the solution you'd like to see
There should be options, whether in a peridot config or in the project itself, that assigns specific hosts to an architecture and allowing the selection of using "static hosts" if applicable or available for all architectures. For peridot configs, there could potentially be an option to send specific packages to some host too, but might be better within the UI.
Peridot should also be deployable to allow KubeVirt instead of managing pods itself.
Have you considered alternative solutions/features? If so, please describe them.
No response
Version and Build Information
Current
Additional Context
No response
The text was updated successfully, but these errors were encountered: