How best confirm decision on (1) partitions, (2) their capabilities and use?

(1) Partitions

Current idea:

• /home (3TB total)
  
  • Can be seen by compute nodes. Data stored on compute nodes until work is done, then moved to /home.
  • Data on /home removed when not actively needed for their cluster work. Can move the data to /storage, for safe-keeping and convenient access.
  • Data is backed up via EZ-Backup.
  • A new user gets 50GB, by default.
  • The process to request more space is (TBD by group).
• /storage (8TB total)
  
  • Can NOT be seen by compute nodes.
  • This is to store data related only to Scheraga research. No personal files.
  • Data is backed up via EZ-Backup.
  • The process to request more space is (TBD by group).
• TBD (1TB)
  • To be used for either expanding /home or /storage at a later date, when we know which needs more space.
• /notbackedup] (4TB)
  
  • For when a researcher needs more temporary space than an individual compute node can provide.
  • Researcher must move data off as soon as they are done with it.
  • This data is NOT BACKED UP. Use only temporarily, and only when a researcher needs "surge" space.
  • No quotas. Thus, potential for researchers to "step on each other".

Community practice: How develop by group, document and share, and reinforce? Good for new researchers and all current researchers.

How determine and get approval for partition sizes?

Current researhcers

Size of /home

Size of /storage

Gia asked:

• Desired quota for /home and /storage?
• How much data to transfer to Matrix as soon as it's available, from local hard drives?

How get approval for process to copy files from old Matrix to the new Matrix?

Idea:

• Create empty /home directories for each user.
• ChemIT copies all a user's data in old Matrix to the new Matrix's "storage" partition. Each researcher selectively moves what is required to their new Matrix home directory.

Group documentation

Community standard of practice

Oliver to move whiteboard outline to here, as a favor

To do's:

Group finds place to host.

• Example: CU's CIT Confluence (such as this page!)

Group identifies owner who can develop  these agreements.

GPU

Yi must test.