Please go here to review a full list of important dates with respect to Alcova and Beartooth Migrations.
HPC Data Migration Policy:
Researchers bear primary responsibility for migrating their data off Beartooth to the new cluster. , MedicineBow
Researchers may begin moving their data from Beartooth to “Data” on June 1stMedicinebow on go-live July 15th, 2024 when the new data storage system will be is available for use.
Researchers should fill out a project migration request to create their project space on ThundererMedicineBow.
If you require assistance when moving data, please include that information in your project migration request available through our service portal.
If you have projects on both Beartooth and Alcova, please fill out two separate migration requests. One for project migrations from Beartooth, and separate request for migrations from Alcova.
All investment, project, and data migrations should be completed and signed off by the project PI by December 1st15th, 2024.
Beartooth /home and /gscratch purges.
Researchers should aware that if you have data hosted on Beartooth in your user account /home or /gscratch that this data will be purged when Beartooth goes offline on December 115th, 2024.
Users should make arrangements to back up this data elsewhere in preparation for Beartooth’s end of life.
Software Migration Policy:
With the understanding that software packages may not run properly if copied directly to our new HPC cluster, we ask instead that all software be reinstalled to the new HPC cluster.
Any software installed on user’s /home (i.e. R libraries and Python packages) will need to re-installed by the user.
Any shared software installations on Beartooth will also need to be re-installedARCC has allocated an additional 250GB for each project in which users may install software specific to their project work.
Directions for new software installations will be made available on June 1st.
A code freeze will be implemented on Beartooth July 115, 2024 and ARCC will not install any new software on Beartooth after this date.
If you require assistance with your software, you may request
thishelp through our portal via a software
installation
.
Alcova Data Migration Policy:
Alcova data is scheduled for migration on a project by project basis.
Migration requests should be created and scheduled by July 1st, 2024.
PIs may fill out project migration requests available on our service portal.
Separate requests should be created for Beartooth migrations. Please do not put your Beartooth and Alcova migration requests in a single form.
Projects may be subject to blackout periods for migration.
Project PIs must should sign off approving their project migrations by July 15, 2024.
Important Dates:
...
June 1st, 2024
New storage system “Data” to be generally available for use.
ARCC will being working with users to begin migration from Alcova to “Data.”
New HPC cluster “Thunderer” enters beta testing.
Software installations directions for “Thunderer” will be available for researchers on our ARCC wiki to begin reinstalling software at the new location.
...
July 1st, 2024
New HPC cluster “Thunderer” becomes generally available to all UWyo researchers.
ARCC will begin working with users to migrate from Beartooth and Alcova, including invested hardware.
Data currently hosted on Alcova should be requested and scheduled for migration.
Code freeze begins for Beartooth. No new software installations may be requested on Beartooth.
...
July 15, 2024
Project PIs should sign off approving their Alcova project migrations.
...
August 1st, 2024
Alcova data should be migrated to new storage system.
...
October 1st, 2024
Deadline for projects in Beartooth to begin migration
...
December 1, 2024
Beartooth \gscratch and \home storage directories purged for all users.
All Investment nodes and project data migrated from Beartooth to Thunderer should be signed off by the PI.
December 15th, 2024
...
31, 2024.