since this relatively simple task evolved from "change few templates" to
"make some decent changes both in foreman and proxy", I've decided to
set a new standard and create our very first Feature wiki page.
I would like to hear your opinions on that, which patch we should take.
Or maybe you have something different on your mind. Share your ideas
now, or never. Also CCing OpenStack folks for some input.
Unfortunately RedMine wiki does not allow us to lists subpages, or I
haven't find a way how. Also note this is not a markdown syntax, but
Textile. I find it less convenient, specifically when it does not eat my
hard-wraps which I use in Vim when editing text files.
If folks want to join me in describing their sprint features, take this
as a first version template. Maybe we can move this to a github repo
(foreman-features) which has markdown (and git, yeah). But this is not
big deal now.
I support "option 2", deploy each boot config and use the DHCP server
logic to provide a different bootloader.
Could you expand on these two changes? I don't understand what they
pertain to:
modify default PXE templates
modify how Foreman deploys default templates
I think you probably need to add support to puppet-dhcp for the
conditional dhcpd logic, as well as the deployment of EFI bootloaders
(already listed).
···
On 03/10/14 13:30, Lukas Zapletal wrote:
> Hey,
>
> since this relatively simple task evolved from "change few templates" to
> "make some decent changes both in foreman and proxy", I've decided to
> set a new standard and create our very first Feature wiki page.
>
> It's here:
>
> http://projects.theforeman.org/projects/foreman/wiki/PXE_Booting_UEFI
>
> I would like to hear your opinions on that, which patch we should take.
> Could you expand on these two changes? I don't understand what they
> pertain to:
>
> - modify default PXE templates
Oh this should been "modify default DHCP template". We need something
similar to what I showed in the design doc (dhcpd.conf). Fixed.
> - modify how Foreman deploys default templates
That's what's needed to deploy default templates. Currently, the REST
API accepts the template content and PXE "flavor". We need to drop the
flavor and require all three templates: PXELinux, Grub 1 and 2.
Note this is an API change. Do we have some blueprints how to do that
properly for the proxy (e.g. existing features/tasks)?
> I think you probably need to add support to puppet-dhcp for the
> conditional dhcpd logic, as well as the deployment of EFI bootloaders
> (already listed).
Right, that was explained above. Yes, the deployment is described in the
RHEL documentation (linked from my blog post, which is linked from the
wiki). Should be relatively easy to implement.
Also CCing OpenStack folks for some input.