Do not use this in production !
It is meant to be used for local development. While it response to the app as a ldap and slurm endpoint, the set up is not designed for production ready security !
Do not use this ssh_host_rsa_key in any production environment or for your own private usage !
The private ssh_host_rsa_key is located for convenience in this repository. It makes sure that the public key fingerprint is always the same for ssh client.
This docker set up provides a local API for ldap and slurm functionality. It does not however support the directory management system. For example I could not make setting the quota of a created directory work properly in a docker container.
By default the conf.toml is set up for docker properly in the repository. In development the key "include_dir_mgmt" needs to false in the conf.toml. The key must be "sacctmgr_path" in the conf.toml file. In the docker container the PATH environment variable includes the sacctmgr executable.
- Go into docker folder relative to the project root
cd ./docker
- build docker image from local files. Only needs to be done once.
./docker_build_set_up.sh
- start docker container
./run_dev_docker.sh
- Wait a bit until slurmdb and slurmctl as services are ready. Then start this post script.
./after_container_start.sh
For stopping all containers
./tear_dev_docker_down.sh
For removing all volumes to clean slurm db and LDAP db
./throw_away_volumes.sh
In the docker set up there is a user called "dev_user". The password of the user is "password" for ssh login.
Use this username and password when the app prompts for ssh credentials during development.
This user has admin rights in the slurmdb and can be used to add/modify/delete users in the slurmdb of the docker set up.
You can also authenticate as the user "dev_user" via a ssh agent. If you want to use or test the functionality with the ssh agent then type the following command:
ssh-add docker/slurm-docker-cluster/dev_user_ed25519
It is presumed that you are at the project root before running the snippet.
- This is accomplished via this script If changes/addition of slurmdb data are required then make changes there.
The folder for slurm cluster came from git clone from this remote Github repository.
It was not included as a sub module because several files needed to modified.
One could make this folder a sub module pointing to our own public fork. This fork should be in the control of university th-nürnberg however.