PXEGrub Enteprise Linux Provisioning

Support
1

Hello,

I am trying to provide EFI for some HP Apollo servers that were just
purchased via Foreman and I am having a hard time implementing it. I have
the dhcpd magic figured out although I found that some of the documentation
available did not work for me, for example my dhcpd.conf ended having this
options:

option architecture code 93 = unsigned integer 16 ;
>
> if option architecture = 00:00 {
>
> option bootfile-name "pxelinux.0";
>
> } elsif option architecture = 00:09 {
>
> option bootfile-name "EFI/shim.efi";
>
> } elsif option architecture = 00:07 {
>
> option bootfile-name "EFI/shim.efi";
>
> } elsif option architecture = 00:06 {
>
> option bootfile-name "EFI/shim.efi";
>
> } else {
>
> option bootfile-name "pxelinux.0";
>
> }
>
>
Instead of what I found on the "official documentation"[1][2]

I have foreman correctly generating the PXEGrub template and by copying the
contents into the right location in the smart-proxy I was able to get the
systems to start the provisioning. But I can't get them to be generated by
default when telling foreman to "build" the host. It always defaults to
PXELinux and If I remove that template from the OS definition and leave
only PXEGrub there the build fails because theOS must have a PXELinux
template associated.

I have to support both types of builds, for the same list of Operating
Systems (EL 6/7). My questions are:

  • Is there a way to have the OS associated only to the PXEGrub template
  • Or even better, is there a way to have the build generate both template
    so it supports both legacy and EUFI boot?

I am unfortunately running a rather old version of Foreman (1.3.2) but if
an upgrade is what will make this work I will have to take the provisioning
outage to do it, but I am not inclined to do it unless absolutely necessary
due to the impending Holidays, the upgrade is schedule for Feb.

Thanks for the help

[1]


[2] https://access.redhat.com/blogs/1169563/posts/1421543

2

Hello,

PXEGrub 2 is only available for RedHat family operating systems, we
recently added a change that it will be also available for Debian families.
For all the others, Foreman insist on PXELinux. Make sure you have the
right family selected. Note EFI is only supported in 1.13+

LZ

··· On Fri, Dec 9, 2016 at 5:25 PM, Telmo X wrote:

Hello,

I am trying to provide EFI for some HP Apollo servers that were just
purchased via Foreman and I am having a hard time implementing it. I have
the dhcpd magic figured out although I found that some of the documentation
available did not work for me, for example my dhcpd.conf ended having this
options:

option architecture code 93 = unsigned integer 16 ;

if option architecture = 00:00 {

option bootfile-name “pxelinux.0”;

} elsif option architecture = 00:09 {

option bootfile-name "EFI/shim.efi";

} elsif option architecture = 00:07 {

option bootfile-name "EFI/shim.efi";

} elsif option architecture = 00:06 {

option bootfile-name "EFI/shim.efi";

} else {

option bootfile-name “pxelinux.0”;

}

Instead of what I found on the “official documentation”[1][2]

I have foreman correctly generating the PXEGrub template and by copying
the contents into the right location in the smart-proxy I was able to get
the systems to start the provisioning. But I can’t get them to be generated
by default when telling foreman to “build” the host. It always defaults to
PXELinux and If I remove that template from the OS definition and leave
only PXEGrub there the build fails because theOS must have a PXELinux
template associated.

I have to support both types of builds, for the same list of Operating
Systems (EL 6/7). My questions are:

  • Is there a way to have the OS associated only to the PXEGrub template
  • Or even better, is there a way to have the build generate both template
    so it supports both legacy and EUFI boot?

I am unfortunately running a rather old version of Foreman (1.3.2) but if
an upgrade is what will make this work I will have to take the provisioning
outage to do it, but I am not inclined to do it unless absolutely necessary
due to the impending Holidays, the upgrade is schedule for Feb.

Thanks for the help

[1] https://github.com/theforeman/rfcs/blob/master/text/0001-
PXE-Booting-UEFI.md
[2] https://access.redhat.com/blogs/1169563/posts/1421543

–
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+unsubscribe@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.

–
Later,
Lukas @lzap Zapletal