Network information
t3ps.najah.edu is the main gateway to infrastructure. The IP is 172.16.1.17 on Najah University Network.
There are a dedicated network for cluster 10.0.0.0/8. The gateway (t3ps.najah.edu) has the IP 10.0.0.1
10.10.0.1xx is for cluster services like puppet, cobbler, condor, squid, ldap
10.10.0.2xx is for Storage infrastructure
10.20.0.xxx is for worker nodes
DHCP Servers and Cobbler
There are a very specific DHCP configuration on the cluster, we have 2 differents DHCP server which will provide IP for the same network.
DHCP on puppet server: will provide DHCP for VM only
DHCP on cobbler server: will provide DHCP for Physical machine only
The reason to have 2 server is due to the fact that cobbler can’t manage Virtual Machine, but Virtual Machine need to have IP from DHCP to make there installation. So, to avoid this issue, we have started a second DHCP server on puppet. This server deliver IP for Virtual Machine only and only during configuration phase.
Both DHCP server are dnsmasq server
On puppet
We configure puppet dnsmasq server to only respond to 52:54:* Mac Address request (a virtual machine).
WARNING! This can be a source of error, if a virtual machine is created with a different mac address this will not work.
/etc/dnsmasq.d/default.conf:
dhcp-range=10.201.0.1,10.201.0.254,255.0.0.0,1h
dhcp-ignore=tag:!known
dhcp-host=52:54:*:*:*:*
dhcp-option=66,10.10.0.101
dhcp-lease-max=1000
On cobbler
dnsmasq configuration is done through cobbler via a template file. This server will provide IP only for machine managed by cobbler.
/etc/cobbler/dnsmasq.template:
read-ethers
addn-hosts = /var/lib/cobbler/cobbler_hosts
dhcp-range=10.201.0.1,10.201.0.254,255.0.0.0,1h
dhcp-ignore=tag:!known
dhcp-option=66,$next_server
dhcp-lease-max=1000
dhcp-authoritative
dhcp-boot=pxelinux.0
dhcp-boot=net:normalarch,pxelinux.0
dhcp-boot=net:ia64,$elilo
$insert_cobbler_system_definitions