You cannot change the assets that we ship. OnDemand is currently failing because it’s trying to recompile the assets - which it can’t. This is what image_tag is trying to do - recompile the assets because logo.svg hasn’t been compiled.
To add an assets, place it in the public directory: /var/www/ood/public and reference it through the href="/public/my_logo.png".
You may be able to use image_tag if you use skip_pipeline: true but honestly I think just writing the HTML is likely safer to just skip rails and whatever rails may try to do altogether.
One more question:
Is it possible to run the jobs on the same node on which OOD is running?
(Not scheduling a job through slurm just running the shell script on the OOD host)
any configuration for this?
These 2 adapters, the systemd and linuxhost may work for you, though they both work over SSH. So the users still have to ssh to localhost, which is counter intuitive, but generally folks use regular login nodes as the destination for these, not the webnode (the node/machine OnDemand is installed on)
So my OOD is installed on the Login node which is connected to the HPC cluster. I am able to schedule jobs on the cluster via slurm.
This is just something I want to experiment with. so inside the cluster.d I have created a .yml file which has a definition for my HPC cluster. Do I need to do something similar if I want to execute the shell scripts on the login node (with OOD)?
Yea you’ll do something similar. Basically OnDemand treats it as another “scheduler” and will use systemd for example to “schedule” work.
You just have to be careful here because an actual scheduler will allocate resources appropriately whereas a single user on a login node can basically crash it for other users if they’re not careful about what they’re doing.
Failed to submit session with the following error:
no implicit conversion of String into Integer
If this job failed to submit because of an invalid job name please ask your administrator to configure OnDemand to set the environment variable OOD_JOB_NAME_ILLEGAL_CHARS.
The Desktop session data for this session can be accessed under the staged root directory.
the config is fine, it works fine with my other cluster config file.
The systemd adapter was a community contribution, so I’m not entirely sure how to debug it.
If the unit is actually gone (I’m sure there’s a way to query current systemd units running) then you can remove the file under ~/ondemand/data/sys/batch_connect/db (I’m recalling that path from memory, it could be slightly off)