RedHat Satellite Kickstart: Passing IP information from Kernel Parameters to Kickstart Config file

galron010 · 03-01-2016, 01:47 PM

Hello,

I am trying to set up an automated Kickstart provisioning process and I have run into a snag. First thing's first, here is what I am currently working with:

OS attempting to install: RHEL 6.7
VM boot source: Custom ISO with Kernel Parameters which provide IP information and KS file location.
Kickstart deployment: Using RedHat Satellite 5.x server to create and store KS config file.

Where I am so far:

I can boot a blank VM off of the ISO and it goes out and grabs the KS file.
IF I configure the IP information in the KS file, the system will continue to the Kickstart process without prompt (if IP information is not configured statically in the KS file, then I am prompted for IP info - this is what I need to avoid).

So, what I need now is to be able to take the network config information from the ISO, and write it to the Kickstart portion.

Here is the ISO boot option I am using:

Code:

label ks
  menu label Install system using ^Kickstart on remote server
  menu default
  kernel vmlinuz
  append text ksdevice=eth0 ip=192.168.1.11 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.200,192.168.2.200 ks=http://my-satellite.domain.net/ks/cfg/org/1/label/ks-config-file initrd=initrd.img

The whole process works so long as I adjust both the ISO and the KS file with the IP information every time. I intend on having a script adjust the ISO automatically, but in the interest of ease, I need to then be able to take this portion from the ISO:

Code:

ip=192.168.1.11 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.200,192.168.2.200

And put it in the Kickstart process where normally the "network" portion of the KS file would provide the information.

What kind of pre-script or other re-configuration could I put in place to make this happen.

I realize this is a long question and a bit convoluted, and I apologize for that, but this is becoming a complex setup. I already know work-arounds I could implement, but right now I need whatever options can be thought of to make the above scenario work as described. If we can't make that work, then I will implement a work-around later.

Thank you all in advanced.

sgrlscz · 03-03-2016, 12:11 PM

I've done something similar in the past, and what I did was in the kickstart, in place of the network configuration, I put:

Code:

%include /tmp/network.inc

Then in the %pre section, I use the following code to turn the command-line options into variables:

Code:

# just in case no network variables
touch /tmp/network.inc
# turn the command-line options into variables
set -- `cat /proc/cmdline`
for I in $*; do case "$I" in *=*) eval $I;; esac; done

Once the variables are setup, you can generate the /tmp/network.inc using the information supplied on the command-line. So for example:

Code:

echo "network --device=$ksdevice --bootproto=static --ip=$ip --netmask=$netmask --gateway=$gateway --nameserver=$dns --activate" >>/tmp/network.inc