Cloud RAS Allocations: Difference between revisions

From Alliance Doc
Jump to navigation Jump to search
(typos)
(Marked this version for translation)
 
(60 intermediate revisions by 14 users not shown)
Line 1: Line 1:
Any Compute Canada user can access modest quantities of compute, storage and cloud resources as soon as they have a Compute Canada account. [https://www.computecanada.ca/research-portal/accessing-resources/rapid-access-service/ 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 [https://www.computecanada.ca/research-portal/accessing-resources/resource-allocation-competitions/ Resource Allocation Competitions] ('''RAC'''). 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:
<languages />
* '''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
<translate>
<!--T:10-->
''Parent page: [[Cloud]]''


<!--T:1-->
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-->
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]].
== Cloud RAS resources limits == <!--T:12-->
<!--T:3-->
{| class="wikitable"
{| class="wikitable"
|-
|-
! Attributes !! Compute Cloud !! Persistent Cloud
! 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
|-
|-
| Who can request || PIs only || PIs only
| vCPUs (see [[Virtual_machine_flavors|VM flavours]]) || 80 || 25
|-
|-
| VCPUs (see [[Virtual_machine_flavors|VM flavours]]) || 79 || 9
| vGPUs<ref name="arbutusonly"/>
|colspan="2" align="center" | 1
|-
|-
| Instances || 20 || 5
| Instances<ref name="softquota">This is a metadata quota and not a hard limit, users can request an increase beyond these values without a RAC request.</ref> || 20 || 10
|-
|-
| Volumes || 2 || 5
| Volumes<ref name="softquota"/> || 2 || 10
|-
|-
| Volume snapshots || 2 || 5
| Volume snapshots<ref name="softquota"/> || 2 || 10
|-
|-
| RAM (GB) || 300 || 45
| RAM (GB) || 300 || 50
|-
|-
| Floating IP || 2 || 2
| Floating IP || 2 || 2
|-
|-
| Persistent storage (GB) || 999 || 999
| Persistent storage (TB)  
|colspan="2" align="center" | 10
|-
|-
| Default duration || 1  year<sup>1</sup>, with 1 month wall-time || 1 year (renewable)<sup>1</sup>
| Object storage (TB)<ref name="arbutusonly">Currently only available at Arbutus.</ref>  
|colspan="2" align="center" | 10
|-
|-
| Default renewal || April<sup>2</sup> || April<sup>2</sup>
| Shared filesystem storage (TB)<ref name="arbutusonly"/>
|colspan="2" align="center" | 10
|-
| Default duration || 1  year<ref name="renwal">This is to align with the RAC allocation period of April-March.</ref>, with 1 month wall-time || 1 year (renewable)<ref name="renwal"/>
|-
| Default renewal || April<ref name="renwal"/> || April<ref name="renwal"/>
|}
|}
<small>
# PI’s may request a 1-year renewal of their persistent cloud for 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 affect in April. 
# This is to align with the RAC allocation period of April-March.
</small>


=== How to request RAS cloud resources ===
== Requesting RAS == <!--T:2-->
In order to use cloud RAS resources, two steps must be completed:
To request RAS, please  [https://docs.google.com/forms/d/e/1FAIpQLSeU_BoRk5cEz3AvVLf3e9yZJq-OvcFCQ-mg7p4AWXmUkd5rTw/viewform fill out this form].
# Principal investigator (PI) request cloud resources and cloud project is created along with PI's cloud account;
# Users sponsored by PI and required access to the cloud project apply for cloud accounts


PIs can request cloud resources within the limits available for RAS and sponsored users can request cloud accounts by completing [https://docs.google.com/forms/d/e/1FAIpQLSf0BF6Lfbc0lH9_Wuos_MVAfM96VXwf0TLMShHSIueZo3dwCA/viewform this on-line form]. PIs must provide, among other things, the following information with their request:
* Why you need cloud resources
* Why the various Compute Canada HPC clusters are not suitable
* Brief description of exactly what resources will be required within the RAS limits
* What your plan is for efficiently using these resources.
* Describe your plans for maintenance and security upkeep ([[Security_considerations_when_running_a_VM|refer to this page]]).


All requests will be received and processed by Compute Canada Cloud admin staff within '''48''' hours. When PI's RAS request is processed a '''''default cloud project''''' is created. PI can have maximum of 3 projects:
* <PI_RAP_name>-dev (Default cloud project. For example: '''''def-jsmith-dev''''')
* <PI_RAP_name>-prod (For example: '''''def-jsmith-prod''''')
* <PI_RAP_name>-<suffix> (For example: '''''def-jsmith-test''''')


All 3 of these cloud projects share the same pool of resources, allocated trough RAS request. To request creation of non-default cloud projects (-dev, -<suffix>), PI needs to submit a support ticket to Compute Canada OTRS (email [mailto:cloud@computecanada.ca cloud@computecanada.ca]).
<!--T:13-->
<small>


All sponsored users' requests for cloud accounts needs to be confirmed by their PI. After such request is received, Compute Canada Cloud admin staff will contact PI via email to confirm sponsored users request for cloud account and to assign with cloud projects, owned by PI, that user can have access to. 
==Notes== <!--T:14-->
 
<references/>
If you have questions or need help, please contact [mailto:cloud@computecanada.ca cloud@computecanada.ca].
</small>
</translate>
[[Category:Cloud]]

Latest revision as of 18:17, 8 September 2023

Other languages:

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. ↑ 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. ↑ 2.0 2.1 2.2 Currently only available at Arbutus.
  3. ↑ 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. ↑ 4.0 4.1 4.2 4.3 This is to align with the RAC allocation period of April-March.

Rapid Access Service

Resource Allocation Competition

Retrieved from "https://docs.alliancecan.ca/mediawiki/index.php?title=Cloud_RAS_Allocations&oldid=143400"