Cloud RAS Allocations: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
(Marked this version for translation) |
||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 6: | Line 6: | ||
<!--T:1--> | <!--T:1--> | ||
Any Digital Research Alliance of Canada user can access modest quantities of resources as soon as they have an Alliance account. Rapid Access Service ( | Any Digital Research Alliance of Canada user can access modest quantities of resources as soon as they have an Alliance account. The Rapid Access Service (<b>RAS</b>) allows users to experiment and to start working right away. Many research groups can meet their needs with the Rapid Access Service only. Users requiring larger resource quantities can apply to our annual [https://alliancecan.ca/en/services/advanced-research-computing/accessing-resources/resource-allocation-competition Resource Allocation Competition] (<b>RAC</b>). Primary Investigators (PIs) with a current RAC allocation are also able to request resources via RAS. | ||
<!--T:11--> | <!--T:11--> | ||
Using cloud resources, researchers can create | Using cloud resources, researchers can create <b><i>cloud instances</b></i> (also known as <i>virtual machines</i> or <i>VMs</i>). There are two options available for cloud resources: | ||
* | * <b>Compute instances</b>: These are instances that have a <b>limited life-time</b> (wall-time) and typically have <b>constant high CPU</b> requirements. They are sometimes referred to as <i>batch</i> instances. Users may need a large number of compute instances for production activities. Maximum wall-time for compute instances is <b>one month</b>. 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. | ||
* | * <b>Persistent instances</b>: These are instances that are meant to run <b>indefinitely</b> and would include <b>Web servers</b>, <b>database servers</b>, etc. In general, these instances provide a persistent service and use <b>less CPU</b> power than compute instances. | ||
* | * <b>vGPU</b>: Arbutus currently offers V100 GPUs in a single flavor (<b>g1-8gb-c4-22gb</b>). This flavor has 8GB GPU memory, 4 vCPUs and 22GB of memory. In the future, alternative GPU flavors will be available; researcher feedback on useful resource combinations for those new flavors is welcomed. For more information on setting up your VM to use vGPUs, see [[Using cloud vGPUs|Using cloud vGPUs]]. | ||
<!--T:12--> | == Cloud RAS resources limits == <!--T:12--> | ||
<!--T:3--> | <!--T:3--> | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
! Attributes !! Compute instances<ref name="both-renewal">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 per storage type. | ! Attributes !! Compute instances<ref name="both-renewal">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 per storage type. PIs 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.</ref> !! Persistent instances<ref name="both-renewal"/> | ||
|- | |- | ||
| | | May be requested by || PIs only || PIs only | ||
|- | |- | ||
| vCPUs (see [[Virtual_machine_flavors|VM flavours]]) || 80 || 25 | | vCPUs (see [[Virtual_machine_flavors|VM flavours]]) || 80 || 25 | ||
| Line 53: | Line 52: | ||
|} | |} | ||
<!--T:2--> | == Requesting RAS == <!--T:2--> | ||
To request RAS, please | To request RAS, please [https://docs.google.com/forms/d/e/1FAIpQLSeU_BoRk5cEz3AvVLf3e9yZJq-OvcFCQ-mg7p4AWXmUkd5rTw/viewform fill out this form]. | ||
Latest revision as of 18:17, 8 September 2023
Parent page: Cloud
Any Digital Research Alliance of Canada user can access modest quantities of resources as soon as they have an Alliance account. The Rapid Access Service (RAS) allows users to experiment and to start working right away. Many research groups can meet their needs with the Rapid Access Service only. Users requiring larger resource quantities can apply to our annual Resource Allocation Competition (RAC). Primary Investigators (PIs) with a current RAC allocation are also able to request resources via RAS.
Using cloud resources, researchers can create cloud instances (also known as virtual machines or VMs). There are two options available for cloud resources:
- Compute instances: 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 instances: 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.
- vGPU: Arbutus currently offers V100 GPUs in a single flavor (g1-8gb-c4-22gb). This flavor has 8GB GPU memory, 4 vCPUs and 22GB of memory. In the future, alternative GPU flavors will be available; researcher feedback on useful resource combinations for those new flavors is welcomed. For more information on setting up your VM to use vGPUs, see Using cloud vGPUs.
Cloud RAS resources limits[edit]
| Attributes | Compute instances[1] | Persistent instances[1] |
|---|---|---|
| May be requested by | PIs only | PIs only |
| vCPUs (see VM flavours) | 80 | 25 |
| vGPUs[2] | 1 | |
| Instances[3] | 20 | 10 |
| Volumes[3] | 2 | 10 |
| Volume snapshots[3] | 2 | 10 |
| RAM (GB) | 300 | 50 |
| Floating IP | 2 | 2 |
| Persistent storage (TB) | 10 | |
| Object storage (TB)[2] | 10 | |
| Shared filesystem storage (TB)[2] | 10 | |
| Default duration | 1 year[4], with 1 month wall-time | 1 year (renewable)[4] |
| Default renewal | April[4] | April[4] |
Requesting RAS[edit]
To request RAS, please fill out this form.
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 per storage type. PIs 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 Currently only available at Arbutus.
- ↑ 3.0 3.1 3.2 This is a metadata quota and not a hard limit, users can request an increase beyond these values without a RAC request.
- ↑ 4.0 4.1 4.2 4.3 This is to align with the RAC allocation period of April-March.