Hello,
Thi is Hariharan who work for Goethe University. I am responsible for installing Open ondemand for our project where we use this for slurm job submisison. I don’t understand few things in the documentation where I tried my best to excute it but no luck.
Before writing my queries, I would like to give a short overview of my open ondemand setup. I have installed and configured open ondemand in proxmox container with non-ssl (http) and we use nginx reverse proxy in another machine which terminates the HTTPS connection and forwards it as http to port 80 of the open ondemand server. The idea is, user hits the hhtps and nginx terminates it and forward it to port 80 of open ondemand server. So the ssl certificates are configured in nginx reverse proxy.
Below are my queries which I need your help:
If I want to set up interatcive apps, then which location should I have to follow? Cause I am confused withbelow two locations. Could you clear me with this?
“/etc/ood/config/apps” or “/var/www/ood/apps/sys”?
Should we have manifest file for each app? Cause I don’t se eanything related to manifest in the official document.
Though I give cluster name in the /etc/ood/config/clusters.d/my_cluster.yml file but again and again it keep htowing the error as “The cluster was never set. Either set it in form.yml.erb with `cluster` or `form.cluster` or
set `cluster` in submit.yml.erb.“
Should we have to give a cluster name only in files.yml or ialso n submit.yml.erb as well? Can you clear me this as I don’t understand.
Though I have followed and configured the following steps in slurm compute node using the below link
but reverse proxy verification is not working yet (section 3.3)
/etc is where you can configure or reconfigure existing applications. /var/www/ood/apps/sys is the location to deploy your applications.
Yes they should all have manifest.yml files. The role key is important here for OnDemand to treat the app as an interactive application when this is set to batch_connect. Beyond that, you also set the icon, category and subcategory here.
You’ve defined the cluster, now you have to use it in your form.yml or form.yml.erb. I.e., you need cluster: my_cluster key and value in your form yml file. So the value here is the name of the file my_cluster. Though with slurm (if you use it) the name of this file should be the actual/real name of the cluster. Supplying the cluster: real_cluster_name in the file is not a good practice as the documentation says, the best practice is to supply a .conf file for that cluster if your on Slurm.
You should only need to supply the cluster name in the form.yml.
As an off the top guess - you need to bounce httpd (or apache2 as the case may be) to get the new configurations from the yml file into the .conf file. Or your host_regex is not working as expected.
I don’t have any new existing application but I have a default one which comes from the installation. In that case do I have to use to the /etc/ood/config/app or the default one /var/ww/ood /apps/?
Regarding this, I am yet to have a clear understanding maybe I have to read a document for batch_connect
Yes, I have defined the cluster under /etc/ood/config/cluster.d/ with a file name g_acct_hlr (/etc/ood/config/cluster.d/g_acct_hlr). So can I use or shouldn’t use the real cluster name in the g_acct_hlr.yml file located under /etc/ood/config/cluster.d/g_acct_hlr.yml?
And shoud I use only the name of the yml file (eg: /etc/ood/config/cluster.d/g_acct_hlr.yml) as a key value in cluster: g_acct_hlr in form.yml file right? Below is my g_acct_hlr.yml file. Can you check the cluster key in both g_acct_hlr.yml and form.ym file and suggest me whteher is this correct or not? Here in my case, cluster name is g_acct_hlr
@harjad84 FYI, we are a very small team of developers (only 3 FTEs), so we can’t commit to providing prompt responses to technical questions (we try to respond whenever we can, but we also just released version 4.1 of Open OnDemand in the past week and there are a lot of other queries coming in from people as well). I’ll note though we do have a support subscription (Subscribe | Open OnDemand) available that gives institutions priority access our our developers for support questions.