Skip to content
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

Staging to main #711

Closed
wants to merge 14 commits into from
7 changes: 3 additions & 4 deletions content/about/people/eubanks.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,10 @@ author = "UVARC Staff"
image = "/images/profiles/profile_adam_eubanks.jpeg"
email = "ucn5xj@virginia.edu"
subjects = [
"video editing/recording",
"machine learning",
"python",
"content creation"
"Open OnDemand",
"Docker"
]
+++

Adam Eubanks is an undergraduate student at the University of Virginia studying Computer Science and French. He specializes in content creation for the RC Learning Team, creating text and video tutorials for the RC Learning Portal. His interests include machine learning, human language, and volleyball.
Adam Eubanks is an undergraduate student at Brigham Young University studying Applied Math. He specializes in Open OnDemand app development and machine learning with HPC, as well as containerization.
5 changes: 4 additions & 1 deletion content/post/2024-july-scratch-purge.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,10 @@ A file’s last access corresponds to the date and time that file was last opene

<code> check-scratch-for-purge > outfile </code>

where <code>outfile</code> is the path of the file to which you wish to save the results.
where <code>outfile</code> is the path of the file to which you wish to save the results. This will save to your `outfile` a list of files ordered from the oldest last accessed to the most recently accessed that will be purged.

Alternatively, you can access the **Check Scratch For Purge** tool available in the *Utilities* dropdown on Open OnDemand. From there, you can view a list of files being purged and save the list to `/home`, `/scratch`, or download it locally.

{{% /accordion-item %}}

{{% accordion-item title="5. What should I do with files that I still need? " id="faq-5" %}}
Expand Down
184 changes: 184 additions & 0 deletions content/post/2024-oct-anaconda-transition.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,184 @@
+++
images = [""]
author = "Staff"
description = ""
date = "2024-10-04T00:00:00-05:00"
title = "Transition from Anaconda to Miniforge module: October 15, 2024"
# url = "/maintenance"
draft = true
tags = ["anaconda"]
categories = ["feature"]
+++

<p class="lead">
Due to the new licensing restrictions by Anaconda on research usage, the licensed Anaconda distribution will be removed from the system on October 15, 2024. The current anaconda/2023.07-py3.11 module will redirect to the miniforge/24.3.0-py3.11 module, switching to conda-forge as the default package installation channel with fewer preinstalled packages. Existing environments will not be affected. However, using Anaconda default channels for research without a personal license will violate the Anaconda license. For instructional use, package installation from licensed channels is still allowed
</p>

# Maintenance: Oct 15, 2024

{{< alert-green >}}The UVA high-performance computing (HPC) system will be down for maintenance on **Tuesday, Oct 15, 2024,** beginning at 6 a.m. The HPC systems are expected to return to full service by 6 a.m. on **Wednesday, Oct 16.**{{< /alert-green >}}

You may continue to submit jobs until the maintenance period begins, but if the system determines your job will not have time to finish, it will not start until the HPC systems are returned to service.

**Questions:** Please contact our <a href="/form/support-request/?category=Storage&request_title=Project%20storage%20data%20migration" class="card-link" target="_blank">user services team</a>, or join us for our [virtual office hours](/support/#office-hours) every Tuesday, 3-5 p.m. and Thursday, 10-12 p.m..


{{% callout %}}
## What to expect after the Oct 15 maintenance?

The licensed Anaconda distribution and base environment provided by the anaconda module will be removed from our systems on Oct 15, 2024. The anaconda module will redirect to the new miniforge/24.3.0-py3.11 module, effectively switching to conda-forge as the only default package installation channel and with a reduced number of preinstalled packages in the base environment.

The use of your existing environments should not be affected by this change. For instructional use you may continue to install python packages from the licensed Anaconda default channels as shown in the example above. However, any use of such environment for research purposes is a violation of the Anaconda license unless you obtained your own license.

We understand that these changes may cause inconvenience, but these changes are mandated by the Anaconda licensing condition which we cannot control. If you have any questions or concerns, please feel free to reach out.

## What to expect after the December 12?



{{% /callout %}}

## FAQ

{{% accordion-group title="Group" id="faqgroup"%}}

{{% accordion-item title="1. How miniforge is different from Anaconda?" id="faq-1" %}}

answer to faq1

{{% /accordion-item %}}

{{% accordion-item title="2. Can I still use my conda environements?" id="faq-2" %}}

answer to faq2

{{% /accordion-item %}}

{{% accordion-item title="3. How to use miniforge to create conda envs?" id="faq-3" %}}

answer to faq3

{{% callout %}}
**Please note:** {{% pi-eligibility %}}
{{% /callout %}}
{{% /accordion-item %}}

{{% accordion-item title="4. Why are we switching from Anaconda to Miniforge?" id="faq-4" %}}

answer to faq4

{{% /accordion-item %}}

{{% accordion-item title="5. Will I lose access to any packages that I had with Anaconda?" id="faq-5" %}}

answer to faq5

{{% /accordion-item %}}

{{% accordion-item title="6. How do I install Anaconda packages if I need them (e.g., licensed or proprietary ones)?" id="faq-6" %}}

answer to faq6

{{% /accordion-item %}}

{{% accordion-item title="7. Can I still use `pip` to install non-Conda packages with Miniforge?" id="faq-7" %}}

answer to faq7

{{% /accordion-item %}}

{{% accordion-item title="8. Will my existing Conda environments work with Miniforge?" id="faq-8" %}}

answer to faq8

{{% /accordion-item %}}

{{% accordion-item title="9. How do I update packages and environments in Miniforge?" id="faq-9" %}}

answer to faq9

{{% /accordion-item %}}

{{% accordion-item title="10. Will my scripts that depend on specific Anaconda packages break when switching to Miniforge?" id="faq-10" %}}

answer to faq10

{{% /accordion-item %}}

{{% accordion-item title="11. What channels are available by default in Miniforge?" id="faq-11" %}}

answer to faq11

{{% /accordion-item %}}

{{% accordion-item title="12. Can I still use the Anaconda repository with Miniforge?" id="faq-12" %}}

answer to faq12

{{% /accordion-item %}}

{{% accordion-item title="13. How do I migrate my existing Anaconda environments to Miniforge?" id="faq-13" %}}

answer to faq13

{{% /accordion-item %}}

{{% accordion-item title="14. How do I get help if I encounter problems during the transition?" id="faq-14" %}}

answer to faq14

{{% /accordion-item %}}

{{% accordion-item title="15. Will miniforge be compatible OOD JupyterLab ?" id="faq-15" %}}

answer to faq15

{{% /accordion-item %}}

{{% /accordion-group %}}


## Announcements

{{% accordion-group title="Comms" id="commsgroup" %}}


{{% accordion-item title="Aug 27, 2024 - Change to Anaconda Module on Our System" id="comm-1" %}}

Dear PI,

This message is important if you intend to use the anaconda/2023.07-py3.11 for your fall classes. Due to the recent licensing restrictions by Anaconda on research usage, we will be removing the licensed Anaconda distribution from our system on October 15, 2024.

As an alternative we have installed the miniforge/24.3.0-py3.11 module, which includes the essential Conda and Mamba package managers along with commonly used packages such as numpy, pandas, matplotlib, etc., from the conda-forge channel.

**How should I prepare?**

Between now and October 15, you may load the existing anaconda module or the newly installed miniforge/24.3.0-py3.11 module. Both modules provide the same conda commands to manage and use your conda environments.

Important: By default, the miniforge distribution will only provide packages from the conda-forge channel. Therefore, if you require packages from channels that are covered by the Anaconda repository Terms of Service (main/anaconda, r, msys2) you may specify this in your installation command but only for environments that are restricted to educational use, i.e., instructional work in your classes. For example, to install the seaborn package from the Anaconda default channels, you would use:

conda install –n path-to-my-conda-env seaborn –c anaconda

**What to expect on October 15, 2024?**

The licensed Anaconda distribution and base environment provided by the anaconda module will be removed from our systems on Oct 15, 2024. The anaconda module will redirect to the new miniforge/24.3.0-py3.11 module, effectively switching to conda-forge as the only default package installation channel and with a reduced number of preinstalled packages in the base environment.

The use of your existing environments should not be affected by this change. For instructional use you may continue to install python packages from the licensed Anaconda default channels as shown in the example above. However, any use of such environment for research purposes is a violation of the Anaconda license unless you obtained your own license.

We understand that these changes may cause inconvenience, but these changes are mandated by the Anaconda licensing condition which we cannot control. If you have any questions or concerns, please feel free to reach out.

At your service, RC staff


Research Computing

E hpc-support@virginia.edu
P 434.243.1107

University of Virginia
P.O. Box 400231
Charlottesville 22902

{{% /accordion-item %}}

{{% /accordion-group %}}
15 changes: 13 additions & 2 deletions content/post/2024-oct-maintenance.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ author = "Staff"
description = ""
date = "2024-10-04T00:00:00-05:00"
title = "HPC Maintenance: Oct 15, 2024"
draft = false
draft = true
tags = ["rivanna", "afton"]
categories = ["feature"]
+++
Expand All @@ -17,7 +17,18 @@ All systems are expected to return to service by **Wednesday, Oct 16** at 6 am.

## IMPORTANT MAINTENANCE NOTES

### Anaconda
### Expansion of /home

To transition away from the Qumulo filesystem, we will migrate all /home directories to the GPFS filesystem and automatically increase each user’s /home directory limit to 200GB.

### Transition from Anaconda to Miniforge module

Due to the recent [licensing restrictions by Anaconda](https://legal.anaconda.com/policies/en/) on research usage, we will be removing the licensed Anaconda distribution from our system on October 15, 2024. The anaconda module will redirect to the new miniforge/24.3.0-py3.11 module, with a reduced number of preinstalled packages in the base environment, but includes the essential Conda and Mamba package managers along with commonly used packages such as numpy, pandas, matplotlib, etc., from the conda-forge channel.
By default, the miniforge distribution will only provide packages from the conda-forge channel. Therefore, if you require packages from channels that are covered by the Anaconda repository Terms of Service (main/anaconda, r, msys2) you may specify this in your installation command but only for environments that are restricted to educational use, i.e., instructional work in your classes.

The use of your existing environments should not be affected by this change. For instructional use you may continue to install python packages from the licensed Anaconda default channels however, any use of such environment for research purposes is a violation of the Anaconda license unless you obtained your own license. More information on preparing for this change is available [here](link).

We understand that these changes may cause inconvenience, but these changes are mandated by the Anaconda licensing condition which we cannot control. If you have any questions or concerns, please feel free to reach out.

### Modules

Expand Down
4 changes: 3 additions & 1 deletion content/service/dac/awards.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ iii) cultivate communities of researchers with shared interests in data and anal
The DAC offers two types of Awards: Small Awards (up to $10,000 worth of services) and Large Awards (up to $100,000).
While the Small Awards are intended to support research tasks for an individual PI or lab, the large Awards are designed to benefit a broader community.

Recipients of the Awards will receive vouchers that may be used toward RC services, such as collaborations with DAC team members or purchase of data storage.
Recipients of the Awards will receive vouchers that may be used toward RC services, such as collaborations with DAC team members or purchase of data storage, or for support from any of the UVA Cores.


## Award Guidelines
Expand Down Expand Up @@ -116,6 +116,8 @@ To apply for the Small Analytics Research Award, the PI will submit a proposal (

<u>Application Requirements for Large Awards</u>:

The objective of the Large Award is to develop comprehensive data resources that will foster a collaborative spirit among researchers at UVA. Therefore, preference will be given to projects that include principal investigators or co-investigators from diverse fields.

For the Large Analytics Research Award, the proposal must include the following:

1. A cover page that includes the project title, and name, title, department, and e-mail address of each the PI(s) and Co-I(s). The Principal Investigator(s) will be the individual(s) responsible for the scientific or technical direction of the project. If more than one PI is included, the first one listed will have primary responsibility for communications with the DAC and the submission of reports. Any listed Co-Is will not have overall responsibility or spending authority as the PI.
Expand Down
2 changes: 1 addition & 1 deletion content/userinfo/hpc/ood/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,7 @@ The Queue Status app provides detailed information on jobs queued and running in

## Check Scratch For Purge

According to [UVA RC policy](/2024/07/reinstatement-of-file-purging-of-personal-/scratch-files-on-afton-and-rivanna), files in the `/scratch` directory that have not been accessed for over 90 days will be permanently deleted or 'purged'. The Check Scratch For Purge app allows you to see which files are at risk of being purged and download a list of their filenames. It displays the output of the command `check-scratch-for-purge`.
According to [UVA RC policy](/2024/07/reinstatement-of-file-purging-of-personal-/scratch-files-on-afton-and-rivanna), files in the `/scratch` directory that have not been accessed for over 90 days will be permanently deleted or 'purged'. The Check Scratch For Purge app allows you to see which files are at risk of being purged and download a list of their filenames. It displays the output of the command `check-scratch-for-purge`, showing a list of files ordered from the oldest last accessed to the most recently accessed.

## Slurm Script Generator

Expand Down
8 changes: 6 additions & 2 deletions content/userinfo/storage.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,9 +89,13 @@ aliases = [ "/storage" ]

{{< storage_main_page_second >}}

Researchers who request space on ICS must first request an Ivy account using the [Ivy request form](https://services.rc.virginia.edu/ivyvm). Further information on Ivy and the ICS can be found [here](/userinfo/storage/sensitive-data/#ivy-central-storage).
Researchers who request space on High-Security Research Standard must first request an Ivy account using the [Ivy request form](https://services.rc.virginia.edu/ivyvm). Further information on Ivy and the High-Security Research storage can be found [here](/userinfo/storage/sensitive-data/#hs-standard-storage).

Ivy Central Storage is accessible by using [Globus](/userinfo/globus/) and connecting to the Ivy DTN.
High-Security Research Standard Storage is accessible by using [Globus](/userinfo/globus/) and connecting to the High-Security DTN.

## Ivy Central Storage (ICS)

Ivy Central Storage has been replaced by High-Security Research Standard storage.

- - -

Expand Down
11 changes: 7 additions & 4 deletions data/service.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,8 @@ service:
snapshots: "Daily snapshots for 1 week"
replication: "No"
backup: "No"
access: "Rivanna, <a href=\"/userinfo/howtos/storage/drive-mapping/\">mountable on local workstation</a>"
access: "Rivanna, Afton, <a href=\"/userinfo/howtos/storage/drive-mapping/\">mountable on local workstation</a>"
filesystem_location: "<code>/project</code>"
highly-sens-ds-compliant: "No"
use_cases: "Ideal for long-term storage of data to be accessed from Rivanna. Research Project storage is ideal for sharing data within a research group and for running jobs with smaller files."
- name: "Research Standard"
Expand All @@ -63,19 +64,21 @@ service:
snapshots: "No"
replication: "No"
backup: "No"
access: "Rivanna, <a href=\"/userinfo/howtos/storage/drive-mapping/\">mountable on local workstation</a>"
access: "Rivanna, Afton, <a href=\"/userinfo/howtos/storage/drive-mapping/\">mountable on local workstation</a>"
filesystem_location: "<code>/standard</code>"
highly-sens-ds-compliant: "No"
use_cases: "Budget solution for storing data that can be accessed by a personal computer or Rivanna. It is not recommended to run Slurm jobs against research standard storage unless absolutely necessary. File operations on Research Standard storage are slower than on Rivanna <code>/home</code>, <code>/scratch</code>, or <code>Research Project</code> storage."
- name: "Ivy Central Storage"
- name: "High-Security Research Standard Storage"
security: "High"
cost: "$45 TB/year"
quota: "1TB increments"
snapshots: "No"
replication: "No"
backup: "No"
access: "Ivy Virtual Machine"
filesystem_location: "<code>/standard</code>"
highly-sens-ds-compliant: "Yes"
use_cases: "Ideal for long-term storage of highly sensitive data and is suitable for computation with smaller file sizes. Files stored in ICS are read-write only."
use_cases: "Ideal for long-term storage of highly sensitive data and is suitable for computation with smaller file sizes. Files stored in High-Security Research Standard are read-write only."
- name: "IvyVM"
label: "Virtual Machine"
footnote: ""
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,11 @@
<td class=""> {{ index $project_storage "access" | markdownify}}</td>
<td class=""> {{ index $standard_storage "access" | markdownify}} </td>
</tr>
<tr>
<td class="">Filesystem Location</td>
<td class="">{{ index $project_storage "filesystem_location" | markdownify}}</td>
<td class="">{{ index $standard_storage "filesystem_location" | markdownify}}</td>
</tr>
<tr>
<td class=""> Highly Sensitive Data Storage Compliant</td>
<td class=""> {{ index $project_storage "highly-sens-ds-compliant" | markdownify}}</td>
Expand All @@ -62,4 +67,4 @@
<td class=""> {{ index $standard_storage "use_cases" | markdownify}} </td>
</tr>
</tbody>
</table>
</table>
Loading
Loading