Changes between Version 1 and Version 2 of access/BomAccessDocumentation/bom-dp9-management/policy


Ignore:
Timestamp:
Jun 23, 2020 3:53:35 PM (7 weeks ago)
Author:
Wenming Lu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • access/BomAccessDocumentation/bom-dp9-management/policy

    v1 v2  
    22
    33[[BR]][[BR]]
    4 === General
     4==== General
    55  * There is no individual soft quota for core users of ''dp9''.
    6   * Usage of **''/scratch/dp9**'' is not currently managed in this scheme.
     6  * Maximum share of a core user on **''/scratch/dp9''** disk space is 30% of total ''dp9'' quota; users with higher usage will be notified daily by email to reduce their usage to under 30%.
    77  * Maximum share of a core user on **''/g/data/dp9''** disk space is 15% of total ''dp9'' quota; users with higher usage will be notified daily by email to reduce their usage to under 15%.
    88  * Maximum share of a core user on **''/g/data/dp9''** inodes is 15% of total ''dp9'' quota; users with excess number of inodes will be notified daily by email to reduce their usage to under 15%.
     
    1111
    1212[[BR]]
    13 === Emergency
    14   * An emergency is a situation with any combinations of the following three scenarios
     13==== Emergency
     14  * An emergency is a situation with any combinations of the following scenarios
    1515    * Total **''/g/data/dp9''** disk space usage exceeds 85%.
    1616    * Total **''/g/data/dp9''** inode usage exceeeds 85%.
    1717    * Total **''mdss''** tape drive usage exceeds 90%.
     18    * Total **''/scratch/dp9''** disk space usage exceeds 90%.
    1819  * When the total usage of **''/g/data/dp9''** disk space exceeds 85%, all users with more than 5T of usage will be notified daily to reduce their usage until the total usage is down below 85%.
    1920  * When the total usage of **''/g/data/dp9''** inodes exceeds 85%, all users with more than 2M inodes will be notified daily to reduce their inodes until the total usage is down below 85%.
    2021  * When the total usage of **''mdss''** tape drive exceeds 90%, all users with more than 50T of usage will be notified daily to reduce their usage until the total usage is down below 90%.
     22  * When the total usage of **''/scratch/dp9''** disk space exceeds 90%, all users with more than 200T of usage will be notified daily to reduce the usage until the total usage is down below 90%.
    2123 
    2224[[BR]]
    23 === Disaster
    24   * A disaster is a situation with any combinations of the following three scenarios
     25==== Disaster
     26  * A disaster is a situation with any or any combinations of the following scenarios
    2527    * Total **''/g/data/dp9''** disk space exceeds 100%.
    2628    * Total **''/g/data/dp9''** inode usage exceeds 100%.
    2729    * Total **''mdss''** tape drive usage exceeds 100%.
     30    * Total **''/scratch/dp9''** disk space exceeds 100%.
    2831    * In a disaster, all jobs submission for project ''dp9'' will be suspended so immediate management action will be taken to address the issue.
    2932    * The goal is reduce the usage of the over-quota resource to sit below 95% of its quota.
     
    4144    * Step 2: Set the threshold to 160T, and reduce all users with usage more than 160T on **''mdss''** to 160T.
    4245    * Step 3: Apply the decrement of 10T to threshold, and reduce users with usage more than the threshold to the level; repeat the process until reaching the goal.
     46  * For **''/scratch/dp9''** disk space, the following steps will be taken sequentially until the goal is reached
     47    * Step 1: Reduce all users with usage more than 30% of total **''/scratch/dp9''** quota (240T of 800T) to 30% of the total quota.  At this time, no set algorithm is specified for the order of files to be deleted for each user for disaster deletion; i.e. users should assume that any files may be deleted.
     48    * Step 2: Set the threshold to 200T, and reduce all users with usage more than 200T on **''/scratch/dp9''** to 200T.
     49    * Step 3: Apply the decrement of 50T to threshold, and reduce users with usage more than the threshold to the level; repeat the process until reaching the goal.
    4350  * If a user is not available, files from the user will be randomly removed from disk and/or tape to meet the target.
    4451
    4552[[BR]]
    46 === Guest users
    47   * Maximum disk space of 0.5T on **''/g/data/dp9''** can be used by a guest user for collaboration work with ''dp9'' core users for up to 6 months.
     53==== Guest users
     54  * Maximum disk space of 500G on **''/g/data/dp9''** can be used by a guest user for collaboration work with ''dp9'' core users for up to 6 months.
     55  * Maximum disk space of 5000G on **''/scratch/dp9''** can be used by a guest user for collaboration work with ''dp9'' core users.
    4856  * Guest users should not use ''dp9'' group resources on **''mdss**'' tape drive.
    4957  * Guest users are reviewed annually in !April/May each year for dp9 membership.
    5058 
    5159[[BR]]
    52 === Aged file management
    53   * Aged files are those which have not been accessed within a year. The aged file management takes place at most once in year on **''/g/data/dp9''**; there is currently no aged file management on **''mdss''** of ''dp9''.
     60==== Aged file management
     61  * Aged files are those which have not been accessed within a year. The aged file management takes place at most once in year on **''/g/data/dp9''**; there is currently no aged file management on **''/scratch/dp9''** and **''mdss''** of ''dp9''.
    5462  * A profile of aged files on **''/g/data/dp9''** is requested from NCI administrators in October each year.
    5563  * If the total size of aged files is less than 20T, the aged file management on **''/g/data/dp9''** will be skipped for that year.