Thread: KUSU Kickstart through network automation!!

Hi,

I would like (not to say I must) to automatize a kusu deployment with kickstart, through nfs. I am using the kusu-ks.cfg generated from a manual deploy, and I am booting the master node with PXE with this ks as param.

The problem is that the RHEL kernel loads first, and takes the kickstart file. Everything goes well until the kusu wizard, but as I've said, I need to automate this, so that noone interacts with it. I know that the RHEL img then calls stage2.img from the images/ folder.

I asume that what I need to do, is give this stage2.img the ks file to automate the process, but I can't find a way to do so. I have already placed the file ks.cfg and kusu-ks.cfg in the top tree directory and in isolinux directory to give a try, but I keep bumping with the kusu wizard!!

What would I need to do to install KUSU in the master node without any human intervention? Is that at least possible? Am I getting something wrong?

Thanks in advance for your help

---
Martin Farias
Intel Cluster Ready Program
Intel Argentina Software Development Center

Hi,

Currently Kusu cannot install a master installer unattended.

Regards,
George

Then why is the kusu-ks.cfg file generated if it's not supposed to be reused by the kickstart system?
Is this at least in the roadmap? If so, when is this likely to be implemented?

Just a guess...could be that passing a ks= argument to the stage2.img line in the /opt/kusu/etc/distro.conf file address this issue? I wanna know if that's a correct path to follow before I start figuring out how to add that there.

stage2.img is the image file that is run after RHEL Installer appears, and I guess that's the one doing the job with the wizard. Am I right?

Thanks for your help George.

Regards,

---
Martin Farias
Intel Cluster Ready Program
Intel Argentina Software Development Center

Hi Martin,

Yes I reckon it does look quite contradictory to have a kickstart file which you cannot use in the root directory. In fact, kusu-ks.cfg is created by the kusu installer as part of the installation process, and is not meant to be used standalone.

By this time, the disk has already been partitioned, and the Kusu repository has been created - you will see that the kusu-ks.cfg does not format the disks, and requires packages that are not part of the normal RHEL repository. If you tried to use kusu-ks.cfg on a standard RHEL install, you would get errors about unfound packages.

Perhaps you might want to explore using Kusu to provision installer nodes? You would still need to install the master installer manually, but you could then provision an installer node using addhost.

HTH,
George