rsnt_translations
56,430
edits
(move Managing RAP Membership to own section, not Basic) |
(Marked this version for translation) |
||
Line 52: | Line 52: | ||
Compute Canada resources are made available to PIs through Resource Allocation Projects (RAP). Researchers are usually working on at least one research project. For reporting purposes, we need to be able to provide statistics on how our facilities are used, but the word “project” is too ambiguous, therefore we use a name which does not have any implicit meanings. Also, computing resources are not allocated to individuals, they are allocated to groups of researchers. The RAP is the group of researchers which resources are allocated to. | Compute Canada resources are made available to PIs through Resource Allocation Projects (RAP). Researchers are usually working on at least one research project. For reporting purposes, we need to be able to provide statistics on how our facilities are used, but the word “project” is too ambiguous, therefore we use a name which does not have any implicit meanings. Also, computing resources are not allocated to individuals, they are allocated to groups of researchers. The RAP is the group of researchers which resources are allocated to. | ||
<!--T:36--> | |||
In general, there are two main types to RAPs: | In general, there are two main types to RAPs: | ||
*Default RAP: A default RAP is automatically created when a PI role is activated. Default and Rapid Access Service quotas for storage and cloud resources are managed via this default RAP. The Default RAP allows PIs and sponsored users to make opportunistic user of compute resources with with default (that is, the lowest) priority. On CCDB, it uses the convention def-username [username is also known as "local account"). | *Default RAP: A default RAP is automatically created when a PI role is activated. Default and Rapid Access Service quotas for storage and cloud resources are managed via this default RAP. The Default RAP allows PIs and sponsored users to make opportunistic user of compute resources with with default (that is, the lowest) priority. On CCDB, it uses the convention def-username [username is also known as "local account"). | ||
Line 71: | Line 72: | ||
* Consent to Collect, Use and Disclose Personal Information | * Consent to Collect, Use and Disclose Personal Information | ||
<!--T:37--> | |||
Once your account has been approved, you will be able to see at any time on CCDB the agreements that you have accepted by going to My Account / Agreements [https://ccdb.computecanada.ca/agreements/user_index] | Once your account has been approved, you will be able to see at any time on CCDB the agreements that you have accepted by going to My Account / Agreements [https://ccdb.computecanada.ca/agreements/user_index] | ||
Line 103: | Line 105: | ||
Click on [https://ccdb.computecanada.ca/me/facilities Local Accounts] and it will give you a list of the consortia with links to click on to get an account at that consortium. Note that consortium or local accounts are needed only to log in to our legacy systems. Users can log in to any of the new national systems with their Compute Canada credentials. | Click on [https://ccdb.computecanada.ca/me/facilities Local Accounts] and it will give you a list of the consortia with links to click on to get an account at that consortium. Note that consortium or local accounts are needed only to log in to our legacy systems. Users can log in to any of the new national systems with their Compute Canada credentials. | ||
= How to manage RAP memberships = | = How to manage RAP memberships = <!--T:38--> | ||
<!--T:39--> | |||
The PI must add sponsored users to a RAP in order for them to access CC resources. PIs can manage RAP memberships at any time on CCDB by adding, removing and assigning roles to sponsored users. There are three RAP membership roles: | The PI must add sponsored users to a RAP in order for them to access CC resources. PIs can manage RAP memberships at any time on CCDB by adding, removing and assigning roles to sponsored users. There are three RAP membership roles: | ||
*Owner: by default, the PI is the sole owner of the RAP and all the allocations associated to that RAP. This cannot be changed. The Owner can add or remove RAP managers and members. | *Owner: by default, the PI is the sole owner of the RAP and all the allocations associated to that RAP. This cannot be changed. The Owner can add or remove RAP managers and members. | ||
Line 110: | Line 113: | ||
*Member: the PI can add any sponsor user as a member of a default project. Sponsored users and co-PI can also be added as members of a RAC project. | *Member: the PI can add any sponsor user as a member of a default project. Sponsored users and co-PI can also be added as members of a RAC project. | ||
<!--T:40--> | |||
RAP membership is represented as a group in LDAP. It defines a group of users that are authorized to submit jobs against the RAPI (which is the Id of the RAP) and share files within the same Unix group. | RAP membership is represented as a group in LDAP. It defines a group of users that are authorized to submit jobs against the RAPI (which is the Id of the RAP) and share files within the same Unix group. | ||