mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-25 23:25:54 +03:00
[GH-ISSUE #351] Investigate possibilites of collaboration with libosinfo #1682
Labels
No labels
Hacktoberfest
Hacktoberfest
bootloader
bsd
bug
confirmed
documentation
duplicate
enhancement
enhancement
enhancement
eol
experimental-merged
freebsd
help wanted
invalid
investigate
ipxe
linux
live-os
memdisk
menu
no-issue-activity
no-issue-activity
pull-request
released
todo
upstream
windows
windows
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/netboot.xyz#1682
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @patrakov on GitHub (Aug 27, 2019).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/351
Originally assigned to: @thelamer on GitHub.
Libosinfo is a project that, among other things, has to maintain locations and kernel command lines for network-based Linux distribution installations. It would be nice to check if there is something that they can install and we don't, and the other way round.
One known missing feature for netboot.xyz, supported by libosinfo, is the command line for unattended installation.
cc: @fidencio
@thelamer commented on GitHub (Jan 2, 2020):
Can you give an example of how you generate network bootable kernel comand lines entries. All the docs I found are programmatic interface options for
get_network_install_resourcesapi class.The main focus of this project seems to be generating preseed and install scripts though, from a project perspective an IPXE bootloader will never support this in an automated fashion. Though we do allow users to customize their own IPXE boot entries to hook in whatever they want.
What do you propose would change from a codebase perspective ?
@fidencio commented on GitHub (Jan 2, 2020):
@thelamer,
Firstly, I'm actually not sure whether using libosinfo would be a good fit or not for netboot.xyz and I am really glad you took some time to investigate that.
libosinfo provides:
Knowing that, I do believe that libosinfo may be useful in case netboot.xyz wants to start VMs and perform unattended installation on those via IPXE (in case it's feasible).
You asked for an example of how you can generate a network bootable kernel command line entry, here you can find what's done on virt-install (which is already using libosinfo): https://github.com/virt-manager/virt-manager/blob/master/virtinst/install/unattended.py#L228
I know, it may not be that easy to follow virt-install's code. If you have interest, I can cook a simple example for you in the next few days (-ETOOLATE right now on my timezone ;-)).
Please, let me know whether it'd be of your interest and we can keep the discussion happening.
Best Regards and, again, thanks for investigating this.
@patrakov commented on GitHub (Jan 2, 2020):
The ground truth about kernel command lines is in this folder: https://gitlab.com/libosinfo/osinfo-db/tree/master/data/install-script. In XSL files, look for
<xsl:template match="/command-line">.OTOH I agree that the project goals and use cases are too different, so let's close this ticket.