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

Slurm now installed on OOD. Slurm configuration updated to have OOD in the slurm cluster.

Started mysql on orthus to get slurmdbd working because without it slurm does not work on ood...

Working at https://osc.github.io/ood-documentation/master/enable-desktops/add-cluster.html ,

Desktop will now attempt to start however we have an error in the *vnc launch command* of all things,

-> It turns out that OOD does not like tigervnc -> Install the turbovnc library and install turbovnc,

• Contents of /etc/yum.repos.d/TurboVNC.repo:

[TurboVNC]
name=TurboVNC official RPMs
baseurl=https://sourceforge.net/projects/turbovnc/files
gpgcheck=1
gpgkey=https://sourceforge.net/projects/turbovnc/files/VGL-GPG-KEY
       https://sourceforge.net/projects/turbovnc/files/VGL-GPG-KEY-1024
enabled=1

Still fails at

VNC_OUT=$(vncserver -log "vnc.log" -rfbauth "vnc.passwd" -nohttpd -noxstartup -geometry 800x600 -idletimeout 0  2>&1)

in the job script with

 Could not start Xvnc.

Unrecognized option: -nohttpd

Ugh, it appears this has been removed from turbovnc as of late. Grep Sledgehammer to the rescue,

[root@ood /]# grep nohttpd * -rn
opt/ood/ondemand/root/usr/share/gems/2.7/ondemand/2.0.23/gems/ood_core-0.17.6/lib/ood_core/batch_connect/templates/vnc.rb:90:                VNC_OUT=$(vncserver -log "#{vnc_log}" -rfbauth "#{vnc_passwd}" -nohttpd -noxstartup #{vnc_args} 2>&1)
opt/ood/ondemand/root/usr/share/gems/2.7/ondemand/2.0.23/gems/ood_core-0.18.1/lib/ood_core/batch_connect/templates/vnc.rb:90:                VNC_OUT=$(vncserver -log "#{vnc_log}" -rfbauth "#{vnc_passwd}" -nohttpd -noxstartup #{vnc_args} 2>&1)

Removing these and will re-try once axis1 is unused (I have only test installed the turbovnc system on axis1).

Okay, tested with -nohttpd removed and some progress,

now apparently require websockify to be installed on axis node. For test purposes, installing this manually on axis1.

https://pypi.org/project/websockify/

A better solution is needed for the rest of the nodes...