I am working in connecting OOD to an Open HPC cluster. I have looked at both your 1.4 and 1.5 VMware versions of OOD. I noticed that when I use a desktop to browse to the 1.4 version I get a nice default Open OnDemand website, however when I do the same for VMware 1.5 I just get a default Apache page.
I also have compiled OOD 1.5 based on the manual directions and installed it as a KVM VM machine setup on the cluster from a VNFS file off the head node. When I browse to that OOD I also only get the default Apache website.
The question is how do I move 1.5 to at least the default OOD web page presentation for a browser?
I also have compiled OOD 1.5 based on the manual directions
Does this mean that you didn’t use the rpm?
When I browse to that OOD I also only get the default Apache website.
When you see only the “default Apache” website, what is the URL in the browser?
When you access OnDemand when Apache is properly configured, a request to the base URL / will redirect you to /pun/sys/dashboard and then the Per User NGINX starts as the authenticated user and serves the dashboard:
I did use the rpm. To build the VNFS image that Open HPC can use to PXE boot nodes including the OOD node it does need to use rpms to build the image that gets
distributed to the nodes. I probably confused the issue when I used the word compiled, sorry about that. Note, both the OOD node that got PXE booted from the Open HPC cluster head node and the version 1.5 VMware version which I downloaded from https://yum.osc.edu/ondemand/images/ and installed in KVM show the default Apache home page and not the OnDemand home page image shown below in the email. One interesting thing is the 1.4 VMware image I had
tested earlier in KVM did show the OnDemand home page image shown below. That makes me wonder if something has changed in version 1.5 versus 1.4?
Here is what I see when I browse to the OOD server.
Note: This was solved in direct communication outside of Discourse and we are documenting for others benefit.
Problem: Disable Apache Test Page
Solution:
Check if /opt/rh/httpd24/root/etc/httpd/conf.d contains welcome.conf. If so, delete or move welcome.conf and restart the httpd24-httpd service. You may also need to clear broswer history.
Other Useful Debugging Tips:
Run ps faux | grep httpd to verify the right Apache is running. (i.e. /opt/rh/httpd24/root/usr/sbin/httpd)
Verify /opt/rh/httpd24/root/etc/httpd/conf.d/ood-portal.conf exsits and contains the correct virtual hosts
If you’re going to https:// but your ood-portal.conf is set to listen to port 80 which is http:// not https://. You’ll need to generate ood-portal.conf that supports SSL or navigate to http://. We recommend using SSL so it’s best to update your ood-portal.conf to support SSL. (Link to documentation about adding SSL)