search

nasa-fornax / fornax-images

Customised Jupyterhub images for the Fornax Platform deployments
BSD 3-Clause "New" or "Revised" License
2 stars 2 forks source link

EHN: user installs to be done in a persistent directory #16

Open bsipocz opened 1 month ago

bsipocz commented 1 month ago

If the default user install path would show to a persistent directory it would ultimately be a nicer user experience, see:

https://github.com/nasa-fornax/fornax-demo-notebooks/pull/347#discussion_r1781418207

The downside, of course, is that package installs will take up valuable space, but I suppose we can trust/instruct users to maintain their installations well.

(And this is also point to https://github.com/nasa-fornax/fornax-images/issues/15 so we don't duplicate packages at user level site-packages directories, but provide them centrally)

zoghbi-a commented 1 month ago

As you point out, installing packages in the user space will quickly deplete their storage and bloat the backup. The best way to handle this for now is to make as much of the required software available as part of the system. I think we have most of them now in the Dev image.

bsipocz commented 1 month ago

I don't mean this to be included in any backups. (Also, why do we need backups?). What about defaulting the location to somewhere under efs/?

zoghbi-a commented 1 month ago

The efs/ is a temporary sharing solution. it is not meant for production.

For backup, it is part of our requirement that the home space is backed up at regular intervals. Installing software there means it will be added to the backup.

I am currently at Roman Platform workshop, and we are having exactly this discussion. They are trying to answer this question too.

bsipocz commented 1 month ago

The efs/ is a temporary sharing solution. it is not meant for production.

OK, but eventually there will be a space sharing solution, or some non-backuped place, I suppose. So all custom installs can land there and be persistent.