I want to emulate SLURM on Ubuntu 16.04. I don't need serious resource management, I just want to test some simple examples. I cannot install SLURM in the usual way, and I am wondering if there are other options. Other things I have tried:
A Docker image. Unfortunately,
docker pull agaveapi/slurm; docker run agaveapi/slurm
gives me errors:/usr/lib/python2.6/site-packages/supervisor/options.py:295: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. 'Supervisord is running as root and it is searching ' 2017-10-29 15:27:45,436 CRIT Supervisor running as root (no user in config file) 2017-10-29 15:27:45,437 INFO supervisord started with pid 1 2017-10-29 15:27:46,439 INFO spawned: 'slurmd' with pid 9 2017-10-29 15:27:46,441 INFO spawned: 'sshd' with pid 10 2017-10-29 15:27:46,443 INFO spawned: 'munge' with pid 11 2017-10-29 15:27:46,443 INFO spawned: 'slurmctld' with pid 12 2017-10-29 15:27:46,452 INFO exited: munge (exit status 0; not expected) 2017-10-29 15:27:46,452 CRIT reaped unknown pid 13) 2017-10-29 15:27:46,530 INFO gave up: munge entered FATAL state, too many start retries too quickly 2017-10-29 15:27:46,531 INFO exited: slurmd (exit status 1; not expected) 2017-10-29 15:27:46,535 INFO gave up: slurmd entered FATAL state, too many start retries too quickly 2017-10-29 15:27:46,536 INFO exited: slurmctld (exit status 0; not expected) 2017-10-29 15:27:47,537 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-10-29 15:27:47,537 INFO gave up: slurmctld entered FATAL state, too many start retries too quickly
This guide to start a SLURM VM via Vagrant. I tried, but copying over my
munge
key timed out.sudo scp /etc/munge/munge.key vagrant@server:/home/vagrant/ ssh: connect to host server port 22: Connection timed out lost connection
So ... we have an existing cluster here but it runs an older Ubuntu version which does not mesh well with my workstation running 17.04.
So on my workstation, I just made sure I
slurmctld
(backend) andslurmd
installed, and then set up a trivialslurm.conf
withafter which I restarted
slurmcltd
and thenslurmd
. Now all is fine:This is a degenerate setup, our real one has a mix of dev and prod machine and appropriate partitions. But this should answer your "can backend really be client" question. Also, my machine is not really called
mybox
but is not really pertinent for the question in either case.Using Ubuntu 17.04, all stock, with
munge
to communicate (which is the default anyway).Edit: To wit:
I would still prefer to run SLURM natively, but I caved and spun up a Debian 9.2 VM. See here for my efforts to troubleshoot a native installation. The directions here worked smoothly, but I needed to make the following changes to
slurm.conf
. Below,Debian64
is thehostname
, andwlandau
is my user name.ControlMachine=Debian64
SlurmUser=wlandau
NodeName=Debian64
Here is the complete
slurm.conf
. An analogousslurm.conf
did not work on my native Ubuntu 16.04.