> This is something that I'm looking for as well, but Foreman TFTP > smart-proxy seems to be missing native "ipxe" variant, that would allow for > creation of <tftp_path>/01-<MAC>.ipxe by calling something like this (based > on syntax for smart-proxy TFTP API described in [3]):
I don't understand how would you download the script from proxy, using HTTP? There is no preconfigured httpd service by default. > - support of more protocols to download config file - HTTP/HTTPS, etc. But no TFTP, right? I am not following why someone would do this. > - support for both UEFI and BIOS (both of which obviously understand iPXE > script/config file making this rather attractive alternative to having to > recognize the boot method of the system and create an appropriate config > files as described in [2] iPXE UEFI is in quite early stage of development, you need to get a recent build (2015). But sure, it's a great option for the future. > Is there a reason why Foreman/Smart-proxy only uses iPXE by chaining > through PXElinux and not natively? Is it hard to add at least on > smart-proxy side? No specific reason, the feature hasn't been delivered yet simply. -- Later, Lukas #lzap Zapletal -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
