The bits beaker needs to automate.

Creating a file called.

etc/0a1042a4-petitboot

in the root directory of the tftp server with the following format.

[root@some-tftp-server etc]# cat hexip-petitboot
default Beaker scheduled job for some-system.beaker.com
label Beaker scheduled job for some-system.beaker.com
kernel http://some-http-web-server.beaker.com/fedora/os/ppc/ppc64/vmlinuz
initrd http://some-http-web-server.beaker.com/fedora/os/ppc/ppc64/initrd.img]
append ks=http://beaker.beaker.com/kickstart/7387 ksdevice=bootif serial netboot_method=grub2

The word "default" is key as it will not autoboot the network device without that.

A admin will make the following dhcp configuration


 host some-system.beaker.com-eth0 {
 hardware ethernet xx:xx:xx:xx:xx:Xx;
 fixed-address some-system.beaker.com;
 option conf-file "etc/hexip-petitboot";
 next-server some-tftp-server.beaker.com;
 }


These systems will be able to use ipmitool so we do not have to worry about any special scripts for rebooting them.

Also when the systems are setup right. There is a implied boot order of network then disk.
So simply removing the file from the tftp will allow the next boot device to continue.
Serving the kernel and intird via tftp is supported as well just never got around to testing it.

Let me know if there are any questions.

(In reply to andrew from comment #1)
> The bits beaker needs to automate.
> 
> Creating a file called.
> 
> etc/0a1042a4-petitboot
> 
> in the root directory of the tftp server with the following format.
> 
> [root@some-tftp-server etc]# cat hexip-petitboot
> default Beaker scheduled job for some-system.beaker.com
> label Beaker scheduled job for some-system.beaker.com
> kernel http://some-http-web-server.beaker.com/fedora/os/ppc/ppc64/vmlinuz
> initrd http://some-http-web-server.beaker.com/fedora/os/ppc/ppc64/initrd.img]
> append ks=http://beaker.beaker.com/kickstart/7387 ksdevice=bootif serial
> netboot_method=grub2
> 
> The word "default" is key as it will not autoboot the network device without
> that.
> 
> A admin will make the following dhcp configuration
> 
> 
>  host some-system.beaker.com-eth0 {
>  hardware ethernet xx:xx:xx:xx:xx:Xx;
>  fixed-address some-system.beaker.com;
>  option conf-file "etc/hexip-petitboot";
>  next-server some-tftp-server.beaker.com;
>  }
> 
> 
> These systems will be able to use ipmitool so we do not have to worry about
> any special scripts for rebooting them.
> 
> Also when the systems are setup right. There is a implied boot order of
> network then disk.
> So simply removing the file from the tftp will allow the next boot device to
> continue.

Thanks Andrew. Do you mean, that post install, we can just remove the config and the system will boot from disk?

(In reply to Amit Saha from comment #5)
> (In reply to andrew from comment #1)
> > The bits beaker needs to automate.
> > 
> > Creating a file called.
> > 
> > etc/0a1042a4-petitboot
> > 
> > in the root directory of the tftp server with the following format.
> > 
> > [root@some-tftp-server etc]# cat hexip-petitboot
> > default Beaker scheduled job for some-system.beaker.com
> > label Beaker scheduled job for some-system.beaker.com
> > kernel http://some-http-web-server.beaker.com/fedora/os/ppc/ppc64/vmlinuz
> > initrd http://some-http-web-server.beaker.com/fedora/os/ppc/ppc64/initrd.img]
> > append ks=http://beaker.beaker.com/kickstart/7387 ksdevice=bootif serial
> > netboot_method=grub2
> > 
> > The word "default" is key as it will not autoboot the network device without
> > that.
> > 
> > A admin will make the following dhcp configuration
> > 
> > 
> >  host some-system.beaker.com-eth0 {
> >  hardware ethernet xx:xx:xx:xx:xx:Xx;
> >  fixed-address some-system.beaker.com;
> >  option conf-file "etc/hexip-petitboot";
> >  next-server some-tftp-server.beaker.com;
> >  }
> > 
> > 
> > These systems will be able to use ipmitool so we do not have to worry about
> > any special scripts for rebooting them.
> > 
> > Also when the systems are setup right. There is a implied boot order of
> > network then disk.
> > So simply removing the file from the tftp will allow the next boot device to
> > continue.
> 
> Thanks Andrew. Do you mean, that post install, we can just remove the config
> and the system will boot from disk?

That's correct once the netboot config file is removed the system will boot the disk. There are some problems with making sure the grub.conf/grubenv is built a certain way. But a post kickstart snippet can correct the problem. See rt#322571 as this is not something beaker needs to deal with more of a rhel/ibm thing.

Thanks Andrew.

Patch: http://gerrit.beaker-project.org/#/c/3886/

Beaker 19.2 has been released.