-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dcache not reliable enough for education #159
Comments
Thank you @BSchilperoort for raising the issue. For education currently we only use the dCache data for generating forcing, so we would also be helped if the |
I tried https://servicedesk.surf.nl/wiki/display/WIKI/Create+a+shared+storage+for+Linux on https://grader35.ewatercycle-nle.src.surf-hosted.nl/ with I was able to run apptainer and plot a netcdf file. Operational steps:
Cons:
Pros:
Todos:
NotesCreate storage item called In ewatercycle-nlesc collab org add secret Create private network for ewatercycle-nlesc Create samba file server
On server Populate
Create teaching machine
Mount samba share
Test
|
Thank you @sverhoeven . I think I got most of that :-). Relating to "(optional) host training material on non-src resources so material can be downloaded during creation of file server.". Maybe we can host this on a repo like Zenodo, 4TU? Or if it is purely for teaching we can even make it available as part of Open Educational Resources? |
We could host the data somewhere, but we would have to decide what exactly, and solve some potential issues:
* Alternative could be a script to generate them from docker images? not sure what's better @sverhoeven **At TU Delft you're can upload 1TB/year for free. Zenodo is max 50GB. |
Occasionally Surf's dcache in not accessible, for hours at a time. This is annoying for researchers (or during demo's). However, if you use ewatercycle for teaching this is terrible.
@sverhoeven suggested rehosting a subset of what's on dcache on a SRC virtual machine, which can then be mounted on the machines which the students will work on.
The text was updated successfully, but these errors were encountered: