Procedure:OnDemandSetup
This page lists various security permission that are involved with OOD,
https://osc.github.io/ood-documentation/latest/installation/modify-system-security.html
It is necessary to permit all to access ports 80, 443 and 5554 (the OOD authenticator)/tcp.
https://leo.leung.xyz/wiki/Open_OnDemand contains a lot of potential underdocumented bugfixes / setup BS.
Step 3 - Authentication setup
- set ssl cert file and keyfile at ood_config.yml:36
- under dex:, set ssl: trye
- utilize most of their given template for LDAP connector, with some minor changes required for our ldap CN/DN/DCs
- During testing, set OIDCSSLValidateServer Off under httpd conf.d/ood-portal.conf or it will not work
At this point OOD is online/available and login works but apps are not configured.
Step 4 - cluster configuration
https://osc.github.io/ood-documentation/latest/installation/add-cluster-config.html
followed by slurm instructions at
https://osc.github.io/ood-documentation/latest/installation/resource-manager/slurm.html
per config documents, we need to setup munge/munged and the cluster munge key as well. It appears this system is able to access the cluster scheduler info outputs.
Step 5 - desktop configuration
https://osc.github.io/ood-documentation/master/enable-desktops/add-cluster.html
Cluster has been added to desktop environment settings for OOD, now complains about finding slurm. So Slurm must be installed on OOD!
Compilation & installation of slurm-21.08.4 on OOD at the same directory as on Orthus.
-> slurm config will need to add OOD to config?
setting up slurm config on ood:
- must have munge-devel installed or it will silently fail to build munge support. One might perhaps speculate that this calls for something more than a tiny, buried not-even-an-error message given how critical munge is to 99% of slurm clusters...
- slurm install path must link to ../etc for slurm bins to find config info