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 6: Line 6:
Virtual machines can be easily replicated. One can take a "snapshot" 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.
Virtual machines can be easily replicated. One can take a "snapshot" 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.


Is the cloud the right place for your work? 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 work flow and environment (see [[What is a scheduler?]]) it is likely a better solution, as there are more [https://www.computecanada.ca/research-portal/national-services/compute/ resources available] for HPC. It is also possible to use tools like [[Singularity]] to run custom software stacks inside containers within Compute Canada 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 [https://www.computecanada.ca/research-portal/national-services/compute/ resources available] for HPC and software is already configured and installed for many common needs. There are also tools like [[Singularity]] to run custom software stacks inside containers within Compute Canada HPC clusters.
If your need isn't served by singularity or HPC batch, then cloud is your solution.


==Using the Cloud==
==Using the Cloud==
38,760

edits

Navigation menu