[chef] Re: Re: Re: Re: Re: Re: Common infrastructure for pxe-bootmenus with syslinux?

[Arnold Krille < >]

Maybe the pxe/pxe_menu could have an empty default recipe and
specialized recipes for tftp and dnsmasq?

Or maybe name it "syslinux" and use it to configure syslinux-menus
regardless where they are placed (the path would be a default-attribute
and maybe an optional parameter to the lwrp).
And have one special recipe to copy the pxe-related files into the tftp-root?
Then one can also use the syslinux-cookbook to built things like
boot-sticks or boot-cds with chef(-solo)... just overengineering a
bit...

- Arnold

On Wed, 9 Oct 2013 13:33:37 -0700 Jesse Nelson 
<
 >
 wrote:
> Maybe the best thing would be for the pxe cook I pushed yesterday to
> end up as a pure library cook and a release on community as pxe_menu.
> Then people can use whatever they want for handling clients and Matt
> can use it in pxe_dust. Instead of tftp_dir and a dep on tftp cook I
> can use a pxe or syslinux  attribute namespace for where to generate
> menu entries.  
> 
> Matt if u look at the precise.rb examples in the cook I uploaded it
> is setup to generate entries for hosts from dhcp bags.  I wrote all
> of his almost 2 years ago, and I was integrating pxe with my dhcp and
> bind cooks. What I uploaded yesterday was a quick hack to make it as
> much a library cook as I could.  I think that's the right way for
> this moving forward (vs directly dropping the LWRP in pxe_dust )   
> 
> All of this started out as pxe_dust. But I needed xenserver and rhel
> support.  This is what I ended up with.
> 
> - Jesse 
> 
> > On Oct 9, 2013, at 12:47 PM, Matt Ray 
> > <
 >
> >  wrote:
> > 
> > I'll definitely take a look at it. I've got a 2.0 branch of pxe_dust
> > that replaces tftp with dnsmasq and adds a handful of other small
> > features. I was talking about adding a boot menu to allow you to
> > select PXE OS installation or to boot the hard drive (the default),
> > this would tie in well. Not sure when I'll have time for it, but I'd
> > take the patches.
> > https://github.com/mattray/pxe_dust-cookbook/tree/2.0
> > 
> > 
> > Thanks,
> > Matt Ray
> > Cloud Integrations Product Lead :: Opscode
> > 512.731.2218 :: 
> > 
 
> > mattray :: GitHub :: IRC :: Twitter
> > 
> > 
> >> On Wed, Oct 9, 2013 at 1:38 PM, Jesse Nelson 
> >> <
 >
> >> wrote: I'll merge pr's and perform basic maintenance just wanted
> >> to get the stuff I had out there for others to use. If you want to
> >> run with it or Matt wants to that's great.
> >> 
> >> There lwrp itself might benefit from some love as it's pre chef 11
> >> and I was using an experiment in nested resource notification.
> >> 
> >> -Jesse
> >> 
> >> 
> >>> On Oct 9, 2013, at 1:51 AM, Arnold Krille 
> >>> <
 >
> >>> wrote:
> >>> 
> >>> Hi,
> >>> 
> >>> Am Tue, 8 Oct 2013 19:23:03 -0700 schrieb Jesse Nelson
> >>> <
 >:
> >>>> I moved the integrated / recipe bits to the examples directory
> >>>> and pushed this code up. This cook has been running in
> >>>> production for some time. Feel free to build on it, and if
> >>>> someone wants to take it over I am happy to give it to ya.
> >>>> 
> >>>> https://github.com/spheromak/pxe-cookbook
> >>> 
> >>> I like that! Thanks!
> >>> 
> >>> There are a few nitpicking things:
> >>> - current tftp cookbook has the tftp-directory in
> >>>  node[:tftp][:directory] instead of node[:tftp][:dir]
> >>> - It should be configurable what the global default on timeout is
> >>> and if there is a timeout at all.
> >>> 
> >>> Do you want pull-request for your repository or should I wait
> >>> until Matt Ray picks it up?
> >>> 
> >>> Have fun,
> >>> 
> >>> Arnold

Attachment: signature.asc
Description: PGP signature