38,760
edits
Cloud/en: Difference between revisions
Jump to navigation
Jump to search
Updating to match new version of source page
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
| Line 2: | Line 2: | ||
We offer [https://en.wikipedia.org/wiki/Cloud_computing#Infrastructure_as_a_service_.28IaaS.29 Infrastructure as a Service] that supports [https://en.wikipedia.org/wiki/Hardware_virtualization virtualization]. | We offer [https://en.wikipedia.org/wiki/Cloud_computing#Infrastructure_as_a_service_.28IaaS.29 Infrastructure as a Service] that supports [https://en.wikipedia.org/wiki/Hardware_virtualization virtualization]. | ||
A user of the cloud will typically create or | A user of the cloud will typically create or <i>spin up</i> one or more virtual machines (VMs or <i>instances</i>). He or she then logs into the VM with administrative privileges, installs any desired software, and runs the software applications needed. These applications could be as diverse as a CPU-intensive analysis of particle physics data, or a web service directed towards scholars of literature and the humanities. The advantage is that the user has complete control over the collection of installed software (the <i>software stack</i>). The disadvantage is that the user must have some degree of experience in installing software and otherwise managing a computer. | ||
Virtual machines can be easily replicated. One can take a | Virtual machines can be easily replicated. One can take a <i>snapshot</i> of a VM which can then be started again elsewhere. This makes it easy to replicate or scale up a service, and to recover from (for example) a power interruption. | ||
If you can fit your work easily into the [https://en.wikipedia.org/wiki/Supercomputer HPC] [https://en.wikipedia.org/wiki/Batch_processing batch] submission workflow and environment (see [[What is a scheduler?]]) it is preferable to work outside the cloud, as there are more [[National systems|resources available]] for HPC and software is already configured and installed for many common needs. There are also tools like [[Apptainer]] to run custom software stacks inside containers within our HPC clusters. | If you can fit your work easily into the [https://en.wikipedia.org/wiki/Supercomputer HPC] [https://en.wikipedia.org/wiki/Batch_processing batch] submission workflow and environment (see [[What is a scheduler?]]) it is preferable to work outside the cloud, as there are more [[National systems|resources available]] for HPC and software is already configured and installed for many common needs. There are also tools like [[Apptainer]] to run custom software stacks inside containers within our HPC clusters. | ||
If your need isn't served by | If your need isn't served by Apptainer or HPC batch, then the cloud is your solution. | ||
=Getting a cloud project= | =Getting a cloud project= | ||
| Line 61: | Line 61: | ||
= Cloud systems = | = Cloud systems = | ||
Your project will be on one of the following clouds: | Your project will be on one of the following clouds: | ||
* [https://beluga.cloud.computecanada.ca Béluga | * [https://beluga.cloud.computecanada.ca Béluga] | ||
* [https://arbutus.cloud.computecanada.ca Arbutus] | * [https://arbutus.cloud.computecanada.ca Arbutus] | ||
* [https://graham.cloud.computecanada.ca Graham] | * [https://graham.cloud.computecanada.ca Graham] | ||