Kiwi is a simple cluster booking mangement tool. It can be viewed as an (over) simplified replacement of SLURM cluster manager. The features of Kiwi include:
- NFS+SSH based cluster info management and viewing
- Booking a node from the cluster with a duration and preventing others from booking the same node when it is in use
- Preventing users from logging into unallocated node via SSH.
- Process cleaning-up by user-id when the booking duration expires or the job is killed
Dependency: python3, psutil, SSH, NFS, gcc
SLURM is great in most of aspects, except that it is a bit complex. The user needs to configure munge, NTP and some more configrations to make it work. When we manage a cluster when the nodes of the cluster occationally leave, join and re-image, we find that installing SLURM and re-configuring SLURM takes too much effort. What we want is simply a node booking system for a few users and a process clean-up system. That's why we develop kiwi.
Kiwi uses NFS to share the states of the nodes. A NFS mounted path should be configured at the installation of Kiwi. The NFS path should be shared by all nodes in the cluster and each node should have the same path. For each node, Kiwi maintains a status file which stores the current allocated user, current job-id, job allocation timestamp and the job duration on the node.
To allocate a node, Kiwi firstly check the status file for the node to make sure it is idle. It then changes the allocated user in the file to indicate that the node is allocated. A house-keeper process is launched at the background on the allocated node, which will kill all processes on that node of the user.
Kiwi also hooks the SSH login event, which is implemented by SSH's PAM feature. It will check if the login user of SSH is the allocated user in the node's status file.
First, you need to install NFS and make sure all nodes can access a NFS directory at the same path. In the following part of this guide, we assume that the NFS root directory is at /nfs
. We will put the shared states of Kiwi at path /nfs/kiwi
. Please change the path in the following command according to the path at your system. Then run the command on each node of the cluster:
git clone https://github.com/Menooker/Kiwi
cd Kiwi
sudo sh ./install.sh /usr /nfs/kiwi
On one of the node in the cluster:
sudo kiwi-manage init-master
This will initialize the shared state directory.
To add a node, run
sudo kiwi-manage add-node --name {host_name} --host {ip_or_host} --port {port}
Note that if you log into a node using ssh [email protected]
, usually {host_name}
above should be "aaa" and {ip_or_host}
above should be aaa.company.com
.
Please also edit /nfs/kiwi/config.json
and change the worker_shared_path
field. In our example, it should be
"worker_shared_path": "/nfs/kiwi/"
If you want to allow some of the users to login the nodes without Kiwi allocation (e.g. admin users), you can add the user names to "worker_ssh_bypass" list.
To enable SSH login filter, you need to edit /etc/pam.d/sshd
on each worker node. (Warning: After you edit this file, users cannot login to the node until they have an allocation on the node via Kiwi, or the user is in "worker_ssh_bypass" list.) Please keep an SSH session alive after you edit this file, so that if anything goes wrong, you can undo your changes in /etc/pam.d/sshd
. Also, please add at least one user to the worker_shared_path
field in the config file, to avoid being blocked by SSH login. Do NOT change this file on your master node.
In /etc/pam.d/sshd
, after the last account XXX XXX
line, add a new line:
account required pam_exec.so /usr/lib/kiwi/ssh_checker.py
You can check if works properly. On the "master" node, run
kiwi alloc -u {username} -w {host} -t 100
ssh {username}@{host}
The following command are used to book and return nodes in the cluster.
kiwi info
kiwi alloc -u {username} -w {host} -t {time_in_seconds}
The username can be omitted if you would like to allocate in the name of the current user on the node. The "host" parameter should be an idle node listed in kiwi info
. The time_in_seconds
parameter should be the duration of the job in seconds. After the time expires, all processes of the user will be killed on the node.
After allocation, users can use ssh to login the node.
kiwi run -u {username} -w {host} -t {time_in_seconds}
The meaning of the parameters are the same of kiwi alloc
kiwi kill -u {username} -w {host}
This will kill the processes of that user on the node and the node will be idle.