Sorry, maybe I was a bit unclear. You do not necessarily need the system entries to kickstart machines, you can also work with menus or, as I meant, with a default entry in pxelinux.cfg. When we use a dedicated cobbler for a cluster, we usually have a menu there with password-protected entries for all our installation profiles, and simply temporarily exchange it with a hardcoded entry for the registration purpose. There are plenty of ways to do it otherwise, e.g. with a %pre script in an otherwise harmless kickstart or a custom boot image which contains cobbler-register, etc.
Greetings Andre ----- Am 29. Apr 2015 um 17:51 schrieb Alan Evangelista [email protected]: > On 04/29/2015 12:29 PM, André Gemünd wrote: >>> Is there a way for me to get the bare metal hardware to tell the >>> cobbler server its mac addresses and auto register somehow. From >>> there maybe I can write a shell script to populate the other needed >>> info. >> yes, we usually use a default that runs a kickstart containing the >> $SNIPPET('cobbler_register'). This will create the system records for >> you. > > I do not understand how an auto-register snippet is useful if you'd need > to add the system > to Cobbler before being able to provision it. Could you explain better? > I'm not familiar with this > part of the code. > > Anyway, copying koan's register.py to all systems and running it to auto > register each system in > Cobbler is a good option. My original suggestion of using arp from > Cobbler server to systems > was more limited. > > > Regards, > Alan Evangelista > > _______________________________________________ > cobbler mailing list > [email protected] > https://lists.fedorahosted.org/mailman/listinfo/cobbler -- André Gemünd Fraunhofer-Institute for Algorithms and Scientific Computing [email protected] Tel: +49 2241 14-2193 /C=DE/O=Fraunhofer/OU=SCAI/OU=People/CN=Andre Gemuend _______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
