cc_staff
158
edits
Frequently Asked Questions about the CCDB: Difference between revisions
Jump to navigation
Jump to search
Frequently Asked Questions about the CCDB (view source)
Revision as of 13:02, 7 March 2019
, 5 years agono edit summary
No edit summary |
No edit summary |
||
| Line 58: | Line 58: | ||
*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 the default (that is, the lowest) priority. On CCDB, it uses the convention <tt>def-profname</tt>. | *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 the default (that is, the lowest) priority. On CCDB, it uses the convention <tt>def-profname</tt>. | ||
*RAC RAP: This RAP is created when the PI receives an award through any of the Resource Allocation Competitions. The RAC RAPI typically takes the form abc-123-ab, with an associated group name typically of the form of <tt>rrg-profname-xx</tt> or <tt>rpp-profname-xx</tt> for HPC allocations, and <tt>crg-profname-xx</tt> or <tt>cpp-profname-xx</tt> for Cloud allocations, depending on the competition. | *RAC RAP: This RAP is created when the PI receives an award through any of the Resource Allocation Competitions. The RAC RAPI typically takes the form abc-123-ab, with an associated group name typically of the form of <tt>rrg-profname-xx</tt> or <tt>rpp-profname-xx</tt> for HPC allocations, and <tt>crg-profname-xx</tt> or <tt>cpp-profname-xx</tt> for Cloud allocations, depending on the competition. | ||
== What is a group name? == | |||
Group name is an alias of the Research Allocation Project Identifier (RAPI). Each RAPI has a unique group name (one-to-one mapping), but it is often easier for users to remember the group name. | |||
Typically, group names follows this convention (where “xx” represents some sequence of digits and letters): | |||
*Default RAP: def-[profname][-xx] | |||
* RRG/HPC resource RAP: rrg-[profname][-xx] | |||
* RPP/HPC resource RAP: rpp-[profname][-xx] | |||
* RRG/Cloud resource RAP: crg-[profname][-xx] | |||
* RPP/Cloud resource RAP: cpp-[profname][-xx] | |||
The group name is used as a POSIX group name with an associated POSIX group ID and is propagated through LDAP in the dn attribute: dn: cn=rpp-username,ou=Group,dc=computecanada,dc=ca | |||
== Who has access to a RAP? == | |||
<b>Default RAP: </b> All of a PI's activated sponsored user roles are always members of the PI's default RAP. That is, confirming sponsorship of a user, confers on them membership in a PI's default RAP. This cannot be modified. However, a PI can at any time deactivate any role they sponsor. | |||
<b>RAC RAP:</b> Membership works differently depending for e RAC RAP has HPC or Cloud resources allocated. | |||
*<b>HPC resources:</b> When a new RAC RAP with HPC resources (e.g. CPU, GPU, storage) is created for a PI, all of their sponsored user roles are automatically set up as members of this RAP.
| |||
*<b>Cloud resources:</b> When a new RAC RAP with Cloud resources allocated is created for a PI, only the PI is added as a member of that RAP.
| |||
The PI can modify the membership of any of their RAC RAPs. The PI can add Compute Canada users with an active account as a members of their RAP, as well as remove one or more sponsored user roles from their RAC RAP and limit them to only be able to access the default RAP. | |||
= Registering for an account = <!--T:18--> | = Registering for an account = <!--T:18--> | ||