Cobbler and the HP SmartStart Scripting Toolkit #2

Cobbler and the HP SmartStart Scripting Toolkit was a quick example of getting the SSSTK set up to boot via Cobbler. This post will add the ability to automatically register the system with cobbler and assign it to a hardware-specific profile. When you have a bunch of systems automatically added to Cobbler, you will just have to apply those configurations that make each host unique (like hostname and IP address).

Once this step is mastered, we can go a bit further in the next post and add customization of the BIOS, BMC, and RAID configurations.

The methods being used here, with separate directories for each tool, allow for, well… separation. You could make one directory, download all the RPMs, extract them, and create one big script to copy them to the booted SSSTK environment. The below method better allows for upgradability, separates out dependencies, and is self-documenting.

Assumptions:

  • Instructions in the first post were followed.
  • Tools like wget and rpm2cpio are installed.
  • Your workflow for kickstarting systems is a little more complex than: netboot the new server, pick a Cobbler menu item, enjoy your new system. *

Read more of this post

Cobbler and the Dell OpenManage Deployment Toolkit #2

Cobbler and the Dell OpenManage Deployment Toolkit was a quick example of getting the DTK set up to boot via Cobbler. This post will add the ability to automatically register the system with cobbler and assign it to a hardware-specific profile. When you have a bunch of systems automatically added to Cobbler, you will just have to apply those configurations that make each host unique (like hostname and IP address).

Once this step is mastered, we can go a bit further in the next post and add customization of the BIOS, BMC, and RAID configurations.

The methods being used here, with separate directories for each tool, allow for, well… separation. You could make one directory, download all the RPMs, extract them, and create one big script to copy them to the booted DTK environment. The below method better allows for upgradability, separates out dependencies, and is self-documenting.

Assumptions:

  • Instructions in the first post were followed.
  • Tools like wget and rpm2cpio are installed.
  • Your workflow for kickstarting systems is a little more complex than: netboot the new server, pick a Cobbler menu item, enjoy your new system. *

* My $EMPLOYER uses multiple hardware models and configurations for a single application. We roll an entire cabinet of new hardware into our datacenter and then power it all up. Our workflow allows for discovery and classification of the hardware models and looks like: netboot the new server (preferably this is the default on new hardware); automatically boot to a default discovery + configuration + regisitration profile; once they appear in Cobbler, manually assign Hostname/IP Address/Kickstart Metadata to each system; wait for each system to reboot and load OS; puppet picks up OS configuration and application installation; enjoy our new systems.
Read more of this post