Draft:Software Installation Policies and Guidelines
Revision as of 19:28, 3 February 2023 by Israel.herrera (talk | contribs)
User login server abuse—what to do?
- TODO: post a terminator whitelist to #apps and try running it manually before letting it loose via a
- The login nodes might be big enough that we have a large gap between the resources cgroups_py tries to keep available and our login policy.
- Checkout the 'arbiter' script again. Describe the functionality of the main R and python environments vs more specific environments like pytorch and tensorflow or domain-specific collections like geopython or DJppytt)Q0
TODO: write a help page on software installation guidelines, use expectations, and limits.
Things we want to see on that page
- Recommendations on using our prebuilt e.nys vs building their own in the context
of speed of customization vs. maintaining functional environments. Focus on R and python at first.
- Curated list Of prebuilt environments for users to reference in the context Of the
above recommendations.
- Published environment.yml files for the popular environments like pytorch, which
users could refer to when starting to build their or use prebuilt containers e.g. pytorch container from NVIDIA.
- Availability of the linux software installed in lapps in ResVault.