Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Steps after Migration to GPFS 5

Open
  • Is something wrong?
#69 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

The issue names no repository file or test; first locate the documentation page covering GPFS5 migration and compare its current post-migration guidance with this text. Done means the page contains the cross-platform hosts-file steps, GPFS5 addresses, verification URL, and support details.

Written by the indexing model from the issue text.

Description

When a user is migrated to the new file system GPFS5, they will need to make changes to their local machine's IP addresses in their/etc/host/. Please see detailed instructions below, they are the same for any OS, see the following instructions:

  1. Open the /etc/hosts file (or equivalent)
  • Windows: Open Notepad as Administrator. Then open the file at C:\Windows\System32\Drivers\etc\hosts
  • Linux/Mac: Open a terminal and run 'sudo nano /etc/hosts'
  1. Add the following lines to the top of the file you opened:
138.26.49.45 rc.uab.edu
138.26.49.58 cheaha.rc.uab.edu
  1. Save the file
  • If using Windows, save the file
  • If using Linux/Mac, use Ctrl+O to save then Ctrl+X to exit

You should then be able to go to https://rc.uab.edu in your browser, sign in, and start using Cheaha. If you however run into any issues, please send a ticket to [email protected] . We also have office hours on Zoom from 10-12 on Monday and Thursday where we would be happy to help debug any problems.

Dominant language
Python
Stars
1
Forks
9
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from uabrc/devops-docs

All issues in uabrc/devops-docs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.