As I never managed to get a good explanation myself in past years when
people were asking for it, can you explain what GPXE does differently,
and how much of the normal PXE chain it replaces, and when you *can't*
use it? Is TFTPd completely out of the equation? The etherboot page
talks about legacy boot ROMs, etc, but doesn't really make the case
for itself. Not arguing
against, but I'd just like to have it explained what it actually does.
In any event, we need to be able to answer that when folks ask, and
it seems the manpage or Wiki, at least, needs to explain usage.
+ ks_mirror_name = string.join(distro.kernel.split('/')[-2:-1],'')
862
FYI -- This seems to imply the distro must be mirrored by Cobbler.
It seems like the code needs to anticipate this this possibility?
--Michael
On Sun, Nov 27, 2011 at 11:58 AM, James Cammarata <[email protected]> wrote:
> Two patches, pushed to my github account:
>
> https://github.com/jimi1283/cobbler/commits/esxi-improvements
>
> The ESXI5 patch requires the gpxe patch, since the only sane way to
> add the support for it to cobbler was via the gpxe process documented
> in the VMware build guide. This allows all of the files to be served
> via httpd, otherwise you have to copy the entire ISO contents to a
> TFTP directory (which required some ugly hacking in cobbler).
>
> The one caveat about the gpxe process is that you must manually copy
> the undionly.kpxe file to your tftp directory. Newer distros package
> the etherboot files, otherwise you'll have to download the files from
> http://etherboot.org/wiki/download and build the file yourself (it's a
> fairly painless process). Another TODO is to make the same setup
> changes for DNSMASQ, right now this only supports ISC DHCPD.
>
> There is a new setting called enable_gpxe, which is used currently
> only when new items are created. There is also a new field for systems
> and profiles by the same name, which sets it on a per-object basis.
> This isn't being used for profiles yet, nor will it work on systems
> without an interface and MAC specified, but when enabled on a system
> with a MAC it will create an entry in dhcpd.conf that is configured to
> chain load the undionly.kpxe file. I plan on adding support for
> generic profiles and systems without a MAC, but it might be a
> some-what convoluted process and I'm trying to work out the best way
> to do it (currently it'd involve chain loading gpxe, and then
> detecting that you don't want to use gpxe and chain loading back into
> the old pxelinux.0 file).
>
> I plan on merging these into master in the near future unless people
> have major issues during testing. Enjoy!
> _______________________________________________
> cobbler mailing list
> [email protected]
> https://fedorahosted.org/mailman/listinfo/cobbler
>
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
