ON installation over PXE

[ilja_l]

Hi,

what would be the best way for installing ON on multiple machines over PXE? I mean, is anakonda-ks.cfg generated by the installer enough to "clone" the machine?

thanks,
Ilja

[frame]

In theory (as we have not yet tested it):

1) you should still use OpenNode installer and provide install tree from OpenNode ISO image over NFS/FTP/HTTP - just you boot host over PXE and access install files over NFS/FTP/HTTP - see CentOS guide here: http://www.centos.org/docs/5/html/5.2/Installation_Guide/ch-pxe.html

2) for kickstart part - Im not so sure here at the moment - we actually do a lot of automated setup (vmbr0 networking, partition sizes, etc) via ks.cfg on ISO installer and we have not yet looked into pxe installs with OpenNode installer - so maybe just providing your anakonda-ks.cfg file would be enough - or some kickstart file merging from ISO ks.cfg will be needed for correct postinstall setup. I can post the ISO ks.cfg file contents if needed.  

[frame]

Not yet 100% sure - but it seems to me that providing your own kickstart file to installer will completely override our kickstart  - so in order to do fully automated installations over PXE I would suggest you to edit ks.cfg taken from OpenNode ISO installer and just replace some lines with lines from your anaconda-ks.cfg - in order to further automate some installer dialogues like root password setting, networking parameters, partitioning, etc.

I'll attach the original OpenNode 1.0 stable ISO installer ks.cfg file.

[ilja_l]

Thanks! Will test it out with another machine soon and post back the results.

[tipsimagi]

could you please post the v1.1 ks.cfg file, and I will pick up where the other gentleman left off.

I'm very interested in using your project as an underlying cloud delivery mechanism but I need to be able to automate the install portion over pxe.

thanks.

[activesys]

Actually you will find the v1.1 kickstart on OpenNode v1.1 ISO - there is a ks/ folder with ks.cfg file inside.

[tipsimagi]

thank you