Steps after Migration to GPFS 5

[iam4tune]

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 support@listserv.uab.edu . We also have office hours on Zoom from 10-12 on Monday and Thursday where we would be happy to help debug any problems.

[wwarriner]

Process for migrating accounts to GPFS5 side as of today. Revisit this process starting April 21.

1. Determine if migration to GPFS5 would cause too many roadblocks.
   1. The researcher must be willing to do so. Clearly communicate the need for some technical expertise (/etc/hosts file modification) and the upcoming April 21-28 shutdown.
   2. Switching to GPFS5 should not cause them to be unable to reach /data/project/ research data. Matt knows how to find this out using Linux group membership data, and we can start a conversation about whether they need to be in those groups. If migrating means they can't access important data, without also migrating a very large project space with many other researchers, it is likely worth keeping them on GPFS4. This step takes some thinking.
   3. Determine if the researcher can modify their /etc/hosts file. Start by asking if they are on a personal computer or a UAB-managed computer. If they are on a personal computer, proceed. Otherwise, suggest they stay with GPFS4.
2. If GPFS5 is the way to go, then...
   1. Work with Mike and JP to migrate.
   2. Communicate how they need to change /etc/hosts, see first post in this issue.
3. Follow up closely until the user confirms successful data access.

[mdefende]

This is basically it with the caveat that if we put a hold on their account for inactivity and migrate their data, they aren't coming back to GPFS 4. So they will have to deal with any consequences of that on their own.

[wwarriner]

I generally agree, unless there are exceptional circumstances. This should be very rare, however. And anyway it will all be moot in a few months, hopefully.