• Created by user-29411, last updated on Aug 25, 2014 1 minute read

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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

(1) Partitions

Current idea:

  • /home
    • 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 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
    • 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).
  • /notbackedup]
    • When a researcher needs more temporary space than an individual compute node can provide
    • This data is NOT BACKED UP. Use only temporarily, when a researcher needs "surge" space.

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?

 

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

Idea:

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

Confirm "notbackedup" partition's use.

Q: No quotas?

  • No labels