Bureaucrats, cc_docs_admin, cc_staff
2,879
edits
(Shorter anchor) |
mNo edit summary |
||
Line 80: | Line 80: | ||
<!--T:49--> | <!--T:49--> | ||
<b>RAC RAP:</b> Membership works differently depending on whether the RAC RAP has HPC or Cloud resources allocated: | <b>RAC RAP:</b> Membership works differently depending on whether the RAC RAP has HPC or Cloud resources allocated: | ||
*HPC resources: At the time a new RAP is created with HPC resources (e.g. CPU, GPU, project storage, nearline storage, etc.), CCDB automatically adds as members of the RAP a) all of a PI's sponsored user roles, <i>and</i> b) all associated Co-PI roles, <i>and</i> c) all sponsored users roles of all of the associated Co-PIs. | *HPC resources: At the time a new RAP is created with HPC resources (e.g. CPU, GPU, project storage, nearline storage, etc.), CCDB automatically adds as members of the RAP a) all of a PI's sponsored user roles, <i>and</i> b) all associated Co-PI roles, <i>and</i> c) all sponsored users roles of all of the associated Co-PIs. Any new role that the PI sponsors <i>after</i> a RAP has been created will also be automatically added as member of the RAP. | ||
*Cloud resources: At the time a new RAP is created with Cloud resources allocated, only the PI is added as a member of that RAP. | *Cloud resources: At the time a new RAP is created with Cloud resources allocated, only the PI is added as a member of that RAP. | ||