We used the Rocks login appliance but made some changes which are stored in the extend-login.xml file. This kickstart file contains partitioning information, installs gnome and kde environments, and adds some firewall configurations. This kickstart file is configured for our hardware and should not be used blindly.
For this example we will install a login node with the following data:
On the head node execute:
[root@grow-prod ~]# insert-ethers
The kickstart file partitions the two hard drives as follows in a RAID 1 configuration. Click here to view the partitioning scheme for our login nodes.
Click here to view the network information for our login nodes.
[root@grow-prod ~]# rocks set host interface ip login-0-0 iface=eth1 ip=128.255.88.51 [root@grow-prod ~]# rocks set host interface name login-0-0 iface=eth1 name=grow-in0 [root@grow-prod ~]# rocks set host interface subnet login-0-0 eth1 public [root@grow-prod ~]# rocks add host route login-0-0 128.255.88.1 eth1 netmask=255.255.254.0 [root@grow-prod ~]# rocks sync config [root@grow-prod ~]# rocks sync host network login-0-0
Log in to login-0-0 (or whichever node is being changed).
[root@login-0-0 ~]# vi /etc/sysconfig/networkChange the GATEWAY variable to equal the head node public ip address(or add GATEWAY variable if it is not present).
NETWORKING=yes HOSTNAME=grow-in0.its.uiowa.edu GATEWAY=128.255.88.1
# Add the GATEWAY variable to this file with the public ip address of your head node
[root@grow-login-0-0 ~]# sudo vi /etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1 HWADDR=00:25:90:0b:16:2b IPADDR=128.255.88.50 NETMASK=255.255.254.0 BOOTPROTO=static ONBOOT=yes MTU=1500 GATEWAY=128.255.88.1
Restart the network by running:
[root@grow-prod ~]# service network restart
That might produce an error message but it seems it can be safely ignored.
This Dokuwiki page is maintained by:
Daniel Squires
University of Iowa
Department of Computer Science
Email: daniel-squires@uiowa.edu