Run OOD in WSL on a Win10 VDI?

Apology in advance for the novice question. What prevents me from using my own instance of OOD on my local instance of WSL for submitting jobs to our campus cluster (or any other), where WSL in turn is running in a Windows 10 VDI? Thanks.


I think the hurdle would be setting that up correctly to submit and be allowed to submit as your user from the laptop to the cluster. I would think you’d hit some issues with user mapping and permissions, but what exactly I don’t know. It’s a very peculiar way to use the software, but I mean, it could probably be done with enough effort. Why not just request the center to install it :slight_smile:

Thanks 10x! for reply and question.

I’d prefer a local test instance in order to become better informed (both as a user and salesman) before I pitch to the center for resources.

Re center installation:

  1. We’d need to allocate a separate “center”-provided, VM server since we don’t allow web services on the cluster login nodes.
  2. The center prefers specific resource requirements, which I haven’t been able to infer so far from reading the docs.
  3. Limitations such as IIRC the current center-provided virtual servers are preferably 8-core vice 16 to avoid NUMA-related performance degradation.
  4. I admittedly don’t know what would be involved in providing secure login to all resources involved.
  5. Other?


I think the following page in the docs might help with the requirements part:

There’s also something like the HPC-toolset-tutorial which is a docker-compose setup that gives you a web front-end for OOD and some clusters to submit to and login to. This may help you wrap your mind around some of the docs and how things work:

And the actual part of the tutorial over OOD once you have it running:

To allow secure logins, OOD will work with various identity providers using Apache modules to handle auth and map the user and groups correctly:

Thanks always for the information.

Is there any guidance on how many FTE’s are needed just to manage OOD? Thanks.

Not many, but it’s really an organization’s choice. It’s not so much to maintain it, it pretty much just runs once you’ve set it up, so failures don’t happen that much to the actual webserver.

Staff time is more likely going to be spent debugging the applications like Rstudio or Jupyter. Or updating the applications themselves to support different features.

Ultimately OOD is submitting jobs to your compute nodes, so failures originating from the modules that are being loaded or OS upgrades are more common than the webserver itself being broken.

I think there’s a lot of staff time put in to set it up and get it going. But once it’s going, it’s pretty much interrupt driven by customer tickets either wanting features out of your apps or apps themselves not working correctly.

That said - we don’t spend a lot of time on our OSC deployment on OnDemand. We generate maybe 1-3 customer tickets a month (a very liberal estimate) and tweak/update our applications sparingly (you can check our github activity for how often we’re updating our production applications and configs).