#
Node Setup
Assuming that your nodes have already been created, and you have access to them, follow the instructions on each of the tabs going from leftmost tab to rightmost tab.
#
On the head node
If there is a firewall, disable it with:
sudo systemctl disable firewalld sudo systemctl stop firewalld
If there is no firewall, run the mask command to prevent it from being set up in future:
sudo systemctl mask firewalld
Disable SELINUX.
sudo setenforce 0
Go to the file
/etc/selinux/config
and change theSELINUX
value todisabled
. This permanently disables SELINUX.# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of three values: # targeted - Targeted processes are protected, # minimum - Modification of targeted policy. Only selected processes are protected. # mls - Multi Level Security protection. SELINUXTYPE=targeted
Set the hostname.
sudo hostnamectl set-hostname chead1.pri.mycluster1.cluster.local
Go to the file
/etc/hosts
and add this:10.50.0.13 chead1.pri.mycluster1.cluster.local chead1.pri chead1 10.50.0.31 cnode01.pri.mycluster1.cluster.local cnode01.pri cnode01 10.50.0.26 cnode02.pri.mycluster1.cluster.local cnode02.pri cnode02
The ip addresses will be different
#
On the first compute node.
If there is a firewall, disable it with:
sudo systemctl disable firewalld sudo systemctl stop firewalld
If there is no firewall, run the mask command to prevent it from being set up in future:
sudo systemctl mask firewalld
Disable SELINUX.
sudo setenforce 0
Go to the file
/etc/selinux/config
and change theSELINUX
value todisabled
. This permanently disables SELINUX.# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of three values: # targeted - Targeted processes are protected, # minimum - Modification of targeted policy. Only selected processes are protected. # mls - Multi Level Security protection. SELINUXTYPE=targeted
Set the hostname:
sudo hostnamectl set-hostname cnode01.pri.mycluster1.cluster.local
Go to the file
/etc/hosts
and add this:10.50.0.13 chead1.pri.mycluster1.cluster.local chead1.pri chead1 10.50.0.31 cnode01.pri.mycluster1.cluster.local cnode01.pri cnode01 10.50.0.26 cnode02.pri.mycluster1.cluster.local cnode02.pri cnode02
The ip addresses will be different
#
On the second compute node.
If there is a firewall, disable it with:
sudo systemctl disable firewalld sudo systemctl stop firewalld
If there is no firewall, run the mask command to prevent it from being set up in future:
sudo systemctl mask firewalld
Disable SELINUX.
sudo setenforce 0
Go to the file
/etc/selinux/config
and change theSELINUX
value todisabled
. This permanently disables SELINUX.# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of three values: # targeted - Targeted processes are protected, # minimum - Modification of targeted policy. Only selected processes are protected. # mls - Multi Level Security protection. SELINUXTYPE=targeted
Set the hostname:
sudo hostnamectl set-hostname cnode02.pri.mycluster1.cluster.local
Go to the file
/etc/hosts
and add this:10.50.0.13 chead1.pri.mycluster1.cluster.local chead1.pri chead1 10.50.0.31 cnode01.pri.mycluster1.cluster.local cnode01.pri cnode01 10.50.0.26 cnode02.pri.mycluster1.cluster.local cnode02.pri cnode02
The ip addresses will be different
Proceed to the next page after completing the instructions in each tab.
#
Testing
If all was successful, then the following should be the case:
It should be possible to ping the other nodes from root on the headnode and vice versa, with just the node name. E.g.
[root@chead1 ~]# ping cnode01 PING cnode01.pri.mycluster1.cluster.local (10.50.0.31) 56(84) bytes of data. 64 bytes from cnode01.pri.mycluster1.cluster.local (10.50.0.31): icmp_seq=1 ttl=64 time=0.737 ms ^C --- cnode01.pri.mycluster1.cluster.local ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.737/0.737/0.737/0.000 ms [root@chead1 ~]# ping cnode02 PING cnode02.pri.mycluster1.cluster.local (10.50.0.26) 56(84) bytes of data. 64 bytes from cnode02.pri.mycluster1.cluster.local (10.50.0.26): icmp_seq=1 ttl=64 time=0.755 ms ^C --- cnode02.pri.mycluster1.cluster.local ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.755/0.755/0.755/0.000 ms [root@chead1 ~]#
The command
sestatus
displays the correct mode for SELinux. It should look like this:[root@chead1 ~]# sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: permissive Mode from config file: disabled Policy MLS status: enabled Policy deny_unknown status: allowed Max kernel policy version: 31
If the node has been rebooted, it may look this instead:
[root@chead1 ~]# sestatus SELinux status: disabled