Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Setup ( one-off)

A sandbox directory must be provisioned to enable app development in Open OnDemand (OOD).
First, we need to allow the user to create sandbox apps by creating a symlink to point to the homedir:

sudo mkdir -p /var/www/ood/apps/dev/<USERNAME>
cd /var/www/ood/apps/dev/<USERNAME>
sudo ln -s /home/<USERNAME>/ondemand/dev gateway

User using <NAME>@agreserch.co.nz would use

sudo ln -s /home/agresearch.co.nz/<NAME>/ondemand/dev gateway

Once complete, the enabled user can try a tutorial, e.g. https://osc.github.io/ood-documentation/latest/tutorials/tutorials-interactive-apps/add-jupyter/copy-app.html to become familiar with the sandbox environment and the steps to clone an app from a repo.

https://openondemand.org/run-open-ondemand#enabled-applications is a catalogue of OOD apps available.

When accessing https://ondemand.eri.agresearch.co.nz via the default, it uses an Azure Application proxy that doesn’t allow all cookies to pass through! A known issue is that the WebSocket connects are breaking.

Developing an app ( adding from an existing Github repo)

  1. Example template for an app https://github.com/nesi/eri-ood-rstudio-server

    1. Highly encourage using the same naming convention for all apps i..e clustername-ood-app

NeSI_GA training summary_2.png

Delete an exiting App

NeSI_GA training summary_2 (1).png

\

\

  • No labels