Cloud RAS Allocations: Difference between revisions
No edit summary |
No edit summary |
||
| Line 38: | Line 38: | ||
|colspan="2" align="center" | 10 | |colspan="2" align="center" | 10 | ||
|- | |- | ||
| Object storage (TB)<ref name="arbutusonly"/> | | Object storage (TB)<ref name="arbutusonly"/>Currently only available at Arbutus</ref> | ||
|colspan="2" align="center" | 10 | |colspan="2" align="center" | 10 | ||
|- | |- | ||
Revision as of 20:28, 28 April 2021
Parent page: Cloud
Any Compute Canada user can access modest quantities of compute, storage and cloud resources as soon as they have a Compute Canada account. Rapid Access Service (RAS) allows users to experiment and to start working right away. Many research groups can meet their needs through using the Rapid Access Service only. Users requiring larger resource quantities can apply to one of our annual Resource Allocation Competitions (RAC). Primary Investigators (PIs) with a current RAC allocation are still able to request resources via RAS.
Using cloud resources such as storage, compute and network, researchers can create cloud instances (also known as Virtual machines or VMs). There are two options available for Compute Canada cloud resources:
- Compute cloud: These are instances that have a limited life-time (wall-time) and typically have constant high-CPU requirements. They are sometimes referred to as ‘batch’ instances. Users may need a large number of compute instances for production activities. Maximum wall-time for compute instances is one month. Upon reaching their life-time limit these instances will be scheduled for deactivation and their owners will be notified in order to ensure they clean up their instances and download any required data. Any grace period is subject to resources availability at that time.
- Persistent cloud: These are instances that are meant to run indefinitely and would include web servers, database servers, etc. In general, these instances provide a persistent service and use less CPU power than compute instances.
Cloud RAS resources limits
| Attributes | Compute Cloud[1] | Persistent Cloud[1] |
|---|---|---|
| Who can request | PIs only | PIs only |
| VCPUs (see VM flavours) | 80 | 25 |
| Instances[2] | 20 | 10 |
| Volumes[2] | 2 | 10 |
| Volume snapshots[2] | 2 | 10 |
| RAM (GB) | 300 | 50 |
| Floating IP | 2 | 2 |
| Persistent storage (TB) | 10 | |
| Object storage (TB)[3]Currently only available at Arbutus</ref> | 10 | |
| Shared filesystem storage (TB)[3] | 10 | |
| Default duration | 1 year[4], with 1 month wall-time | 1 year (renewable)[4] |
| Default renewal | April[4] | April[4] |
To request RAS, please fill out this form online.
Notes[edit]
- ↑ 1.0 1.1 Users may request both a compute and persistent allocation to share a single project. Storage is shared between the two allocations and is limited to 10TB/PI in total. PI’s may request a 1-year renewal of their cloud RAS allocations an unlimited number of times; however, allocations will be given based on available resources and are not guaranteed. Requests made after January 1 will expire March of the following year and therefore may be longer than 1 year. Allocation requests made between May-December will be less than 1 year. Renewals will take effect in April.
- ↑ 2.0 2.1 2.2 This is a metadata quota and not a hard limit, users can request an increase beyond these values without a RAC request.
- ↑ 3.0 3.1 Cite error: Invalid
<ref>tag; no text was provided for refs namedarbutusonly - ↑ 4.0 4.1 4.2 4.3 This is to align with the RAC allocation period of April-March.