Here's my situation. I have a tool that builds ISOs from a custom
database of host information (the database is actually the back end of a
control tool for a service my organization provides. The ISO builder is
a subset of this larger tool).
The ISO generator was originally built against 6.2, and the ks.cfg it
generated did an echo to /etc/sysconfig/network-scripts/ifconfig-bond0
because 6.2 allegedly didn't support LACP bonding.
Since the network devices are already configured for LACP when our
servers are plugged in
We're going to upgrade ~400 servers to 6.5 (reinstall, not in-place
upgrade) and since 6.5 supports LACP I've been trying to figure out how
build ks.cfg that can get the network up during the install.
I tried using a network line that had --bondslaves=link, but that didn't
work at all.
Right now I'm going to call a python script in %pre that generates the
three network lines I need (--device=bond0, --device=physical1 and
--device=physical2) and %includes this file.
One question I have is that in the notes for %pre is that the network is
available but DNS is not up. Is this the case? What do I have to call to
reset the network?
Another question is "is this the best way to do it, or did I miss
something in Redhat's copious, thorough and complete documentation".
Regards,
Petro.
:wq
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
