2009/1/7 Ladislav Slezak
Yes, the functionality is very basic, it sets up a selected network service and copies CDs/ISOs to the shared directory. Small and good! I'm using that in my "beta" autoinstall system now.
A small add-on in SLP service configuration. That's because to set up an installation server is complex and the configuration also depends on the target machines (special boot parameters like vga=???). Autoyast installation makes the config even more complicated.
Well yeas and now. It's actually quite easy to make a network boot with autoyast if someone has prepared that autoyast file in advance. What I was thinking of as an idea was to distribute autoyast files that matches a machien config. Ie. an EE901 has a downloaodable autoyast file, a Acer A110 another and so on. Then another medium skilled user can easily install a tested openSUSE config really fast. (and maybe even new users if the install server can be distributed in a image :-) )
We should find a compromise between simple but limited PXE config and generic but hard to use (and implement) approach. Yes! Keep it simple! (as possible...)
Currently there is "Announce as Installation Service with SLP" check box. I could add a new check box "Add to PXE boot config" there. Great!!
In short, these steps are required to setup the boot server: - install needed packages (tftp, syslinux) - configure tftp service and start it (yast2-tftp-server package can be reused here) - copy PXELINUX to /tftpboot dir - create initial PXELINUX config file Yes , that looks good. But should not the tftpboot directory be placed in /srv/tftpboot? I do find it inconsistent to have it on the root. My local config is placed on /srv. Also the DHCP should add the nextserv parameter (if the DHCP is on the same host)
(Yast should check if the boot server has been already set up and should not change it in that case.) Agreed.
These steps are needed when a new product is added - copy the kernel and initrd from CD/ISO to /tftpboot (there might be more kernels available, ask user which should be added?) - add a new boot entry to PXELINUX config (with possibility to edit the kernel command line) each new product should have a separate directory in the tftpboot dir to avoid having to rename the kernels as that is confusing
The PXELINUX config must be updated when - a product is renamed (different path in the installation URL) - the network service is changed (e.g. from NFS to FTP install server) Agreed. And if the autoyast file is updated :-)
It looks not too hard to implement it yast instserver (I think that the PXELINUX config update will be the most problematic part).
Any comments/ideas?
It would be good also to add (or atleast think of ) adding a structured storage for the autoyast files. My current setup places them in /srv/ftp/distros/autoyast This location could then also be set as default storage location in the autoyast editor. cu / birger.... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org