Michael DeHaan wrote:
Joseph Boyer Jr. wrote:
Is there a way in cobbler today that automates using the MAC address for eth0 as the parameter place on the kernel line for the ksdevice, i.e. ksdevice=00:2c:3e:23:4d:1e instead of the default using ksdevice=eth0 or whichever device you specify in the /etc/cobbler/settings file.
I know that passing ksdevice = {My MAC} on the kernel options line in system settings works, but I am looking for something that requires no user intervention. That is I want to use the interface’s MAC address as my default.
This is because of NIC enumeration issue on HP Blade Centers.
I could see this as possible. Two options here -- file an RFE in Trac (fedorahosted.org/cobbler), or implement support for it.
I don't think the patch would be too painful -- adding a boolean option to each interface that says --use-as-explicit-ksdevice that would only be legal /if/ the mac was enabled.
This would be a slightly involved patch -- should mostly involve item_system.py and the "blender" code that evaluates the object tree in utils.py -- but doable.
The RFE list in cobbler is very long so I can't say this is something I would knock out soon. But if someone else finds it interesting maybe they could help.
--Michael
I've previously done this by adding a trigger that looked up the mac address from our ldap server. In theory, you could make a trigger that would grab it from the cobbler api. Another option, possibly simpler and certainly more robust than another command-line flag, but one that could, in rare cases, cause unintended behavior would be to run the kopts string through cheetah, thus allowing one to do 'cobbler system edit --name=spam --mac=$mac_address'.
Ben