Ignacio,

I'm using sis to clone SLES9 machines. This version supports also
conventional naming (ifcfg-eth0 for example), so I think it should be
the same also for SuSE 10.

In my case, since I've a lot of interfaces per node I've resoved it with
the simple post-install script. It parses the hosts_ip file, gets
informations for _all_network interfaces (the explicit device name ethN
must be specified as the first field in the hosts_ip file) and generates
all the /etc/sysconfig/network/ifcfg-* files.

I attach also an example of the hosts_ip file... keep attention at the
netmasks generation! In my case I've only 2 netmasks, so I did it with a
simple text replace (with sed). If you have a lot of different netmasks
you can consider to use for example another field in the hosts_ip file..
Hope this helps...

Regards,
-Andrea

===========================================
script: /var/lib/systemimager/scripts/post-install/50all.network_setup
===========================================

#!/bin/bash

. /tmp/post-install/variables.txt
DEST_PATH=/etc/sysconfig/network
HOST_IP_FILE=/tmp/post-install/hosts_ip

for interface in `cat $HOST_IP_FILE | grep $HOSTNAME | cut -d " "  -f 1`; do

device_ip=`cat $HOST_IP_FILE | grep $HOSTNAME | grep $interface | cut -d
" "  -f 2`

# Resolve netmask.
netmask=`echo $device_ip sed "s/^10.100.*/255.0.0.0/" | sed
"s/^10.10\..*/255.255.255.0/"`

cat << EOF > $DEST_PATH/ifcfg-$interface
DEVICE=$interface
BOOTPROTO=static
STARTMODE=onboot
IPADDR=$device_ip
NETMASK=$netmask
EOF

done

===================================
file: /var/lib/systemimager/scripts/post-install/hosts_ip
===================================

eth0 10.10.64.1                 node01
eth0 10.10.64.2                 node02
eth0 10.10.64.3                 node03
eth0 10.10.64.4                 node04
eth0 10.10.64.5                 node05
eth0 10.10.64.6                 node06
eth0 10.10.64.7                 node07
eth0 10.10.64.8                 node08
eth0 10.10.64.9                 node09
eth0 10.10.64.10                node10
eth0 10.10.64.11                node11
eth0 10.10.64.12                node12
eth0 10.10.64.13                node13
eth0 10.10.64.14                node14
eth0 10.10.64.15                master1

eth2 10.100.8.38     master1
eth2 10.100.8.39     master2
eth2 10.100.8.40     node01
eth2 10.100.8.41     node02
eth2 10.100.8.42     node03
eth2 10.100.8.43     node04
eth2 10.100.8.44     node05
eth2 10.100.8.45     node06
eth2 10.100.8.46     node07
eth2 10.100.8.47     node08
eth2 10.100.8.48     node09
eth2 10.100.8.49     node10
eth2 10.100.8.50     node11
eth2 10.100.8.51     node12

eth3 10.10.66.1      node01
eth3 10.10.66.2      node02
eth3 10.10.66.3      node03
eth3 10.10.66.4      node04
eth3 10.10.66.5      node05
eth3 10.10.66.6      node06
eth3 10.10.66.7      node07
eth3 10.10.66.8      node08
eth3 10.10.66.9      node09
eth3 10.10.66.10     node10
eth3 10.10.66.11     node11
eth3 10.10.66.12     node12


Ignacio Verona wrote:
> Hi! Please, have any one cloned a Suse 10 gold-client? It seems that is
> not easy to cope with network cards because SuSe links the NIC
> configuration with the MAC of that interface, so that's the problem I'm
> facing now. I hope not to need to reconfigure each node by hand, because
> I'm with a 25 nodes cluster!
> 
> Thanks in advance,
> Ignacio.
> 


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to