Cloud: Difference between revisions

Jump to navigation Jump to search
18 bytes added ,  9 months ago
no edit summary
No edit summary
No edit summary
Line 5: Line 5:


<!--T:2-->
<!--T:2-->
A user of the cloud will typically create or "spin up" one or more virtual machines (VMs or "instances"). 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 "software stack"). The disadvantage is that the user must have some degree of experience in installing software and otherwise managing a computer.
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.


<!--T:3-->
<!--T:3-->
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 <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.


<!--T:6-->
<!--T:6-->
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 Singularity or HPC batch, then the cloud is your solution.
If your need isn't served by Apptainer or HPC batch, then the cloud is your solution.


=Getting a cloud project= <!--T:10-->
=Getting a cloud project= <!--T:10-->
rsnt_translations
53,464

edits

Navigation menu