38,760
edits
Cloud/en: Difference between revisions
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 1: | Line 1: | ||
<languages /> | <languages /> | ||
We offer an [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 "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 "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. | ||
| 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. | ||
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 [[Singularity]] to run custom software stacks inside containers within | 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 [[Singularity]] 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 Singularity or HPC batch, then the cloud is your solution. | ||
=Getting a Cloud project= | =Getting a Cloud project= | ||
* Review and understand the [[Cloud shared security responsibility model|important role]] you are about to take on to [http://www.science.gc.ca/eic/site/063.nsf/eng/h_97955.html safeguard your research] and the shared cloud | * Review and understand the [[Cloud shared security responsibility model|important role]] you are about to take on to [http://www.science.gc.ca/eic/site/063.nsf/eng/h_97955.html safeguard your research] and the shared cloud infrastructure. | ||
* If you do not have | * If you do not have an account with us, create one with [https://www.computecanada.ca/research-portal/account-management/apply-for-an-account/ these instructions]. | ||
* A [[OpenStack#Projects|project]] is an allocation of resources for creating VMs within a cloud. | * A [[OpenStack#Projects|project]] is an allocation of resources for creating VMs within a cloud. | ||
* If you are a primary investigator (PI) with an active cloud resource allocation (see [https://www.computecanada.ca/research-portal/accessing-resources/resource-allocation-competitions/ RAC]) you should already have a project. See the below section [[Cloud#Using the Cloud|using the cloud]] to get started. If not or if you are not sure please contact [[Technical support|technical support]]. | * If you are a primary investigator (PI) with an active cloud resource allocation (see [https://www.computecanada.ca/research-portal/accessing-resources/resource-allocation-competitions/ RAC]) you should already have a project. See the below section [[Cloud#Using the Cloud|using the cloud]] to get started. If not or if you are not sure please contact [[Technical support|technical support]]. | ||
| Line 23: | Line 23: | ||
==Preparing your request== | ==Preparing your request== | ||
* When requesting access to an existing project you will need to know the project name and which cloud it is on. See the section on [[OpenStack#Projects|projects]] for guidance on how to find the project name and the section about [[Cloud#Cloud_systems|cloud systems]] for a list of | * When requesting access to an existing project you will need to know the project name and which cloud it is on. See the section on [[OpenStack#Projects|projects]] for guidance on how to find the project name and the section about [[Cloud#Cloud_systems|cloud systems]] for a list of our clouds. Requests for access must be confirmed by the PI owning the project. | ||
* When requesting either a new project or an increase in quota for an existing project some justification, in the form of a few sentences, is required: | * When requesting either a new project or an increase in quota for an existing project some justification, in the form of a few sentences, is required: | ||
**Why you need cloud resources | **Why you need cloud resources | ||
| Line 33: | Line 33: | ||
= Using the Cloud = | = Using the Cloud = | ||
* If you are a first time user: | * If you are a first time user: | ||
**Log in to the [[Cloud#Cloud_systems|cloud]] where you have a [[OpenStack#Projects|project]]. Authenticate using your Compute Canada | **Log in to the [[Cloud#Cloud_systems|cloud]] where you have a [[OpenStack#Projects|project]]. Authenticate using your CCDB (Compute Canada data base) username (not your email address). | ||
**To create your first VM, read the [[Cloud Quick Start|cloud quick start]] guide. | **To create your first VM, read the [[Cloud Quick Start|cloud quick start]] guide. | ||
**See the [[Cloud troubleshooting guide|troubleshooting guide]] for steps to deal with common issues in cloud | **See the [[Cloud troubleshooting guide|troubleshooting guide]] for steps to deal with common issues in cloud | ||
| Line 60: | Line 60: | ||
* [https://graham.cloud.computecanada.ca Graham] | * [https://graham.cloud.computecanada.ca Graham] | ||
* [http://cedar.cloud.computecanada.ca Cedar] | * [http://cedar.cloud.computecanada.ca Cedar] | ||
The details of the underlying hardware and | The details of the underlying hardware and OpenStack versions are described on the [[cloud resources]] page. The [[System status]] wiki page contains information about the current cloud status and future planned maintenance and upgrade activities. | ||
= Support = | = Support = | ||