38,760
edits
Technical glossary for the resource allocation competitions/en: Difference between revisions
Technical glossary for the resource allocation competitions/en (view source)
Revision as of 20:32, 2 September 2020
, 4 years agoUpdating 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: | ||
'''VCPU:''' Stands for virtual central processing unit. One or more VCPUs are assigned to every Virtual Machine (VM) within a cloud environment. Each VCPU is seen as a single physical CPU core by the VM’s operating system. | '''VCPU:''' Stands for virtual central processing unit. One or more VCPUs are assigned to every Virtual Machine (VM) within a cloud environment. Each VCPU is seen as a single physical CPU core by the VM’s operating system. | ||
'''VGPU:''' Stands for virtual graphics processing unit (VGPU). One or more VGPUs can be assigned to Virtual Machines (VM) within a cloud environment. Each VGPU is seen as a single physical GPU core by the VM's operating system. | |||
== Resource allocations == | == Resource allocations == | ||
| Line 76: | Line 78: | ||
'''Service Portal:''' Compute Canada hosts many research web portals which serve datasets or tools to a broad research community. These portals generally do not require large computing or storage resources, but may require support effort by the Compute Canada technical team. Groups applying for a service portal often use the Compute Canada cloud, generally require a public IP address, and may (or may not) have more stringent up-time requirements than most research projects. This option is shown as “Portal” in the online form. | '''Service Portal:''' Compute Canada hosts many research web portals which serve datasets or tools to a broad research community. These portals generally do not require large computing or storage resources, but may require support effort by the Compute Canada technical team. Groups applying for a service portal often use the Compute Canada cloud, generally require a public IP address, and may (or may not) have more stringent up-time requirements than most research projects. This option is shown as “Portal” in the online form. | ||
'''Virtual Machine (VM):''' See Instance above. | '''Virtual Machine (VM):''' See Instance above. | ||
| Line 84: | Line 84: | ||
'''Volume Snapshot:''' A point-in-time copy of an OpenStack storage volume. Used for backups or as a base to instantiate (launch) other VMs. | '''Volume Snapshot:''' A point-in-time copy of an OpenStack storage volume. Used for backups or as a base to instantiate (launch) other VMs. | ||
'''Persistent cloud storage:''' The maximum amount of storage (GB) that can be used by your persistent, reliable block devices. | |||
'''Object Storage:''' persistent object storage used to store large amounts of data that is mostly read access (such as images and data sets). This is considered 'bulk' storage. Accessible from anywhere in the world. Offered as S3 and Swift protocols. Measured in TB. | |||
'''Shared Filesystem Storage:''' persistent storage offered as a Unix-compliant file system that can be mounted across multiple hosts in a tenant. This is useful for sharing data across multiple hosts. Service runs on CephFS and requires either a Fuse driver (Windows/Linux) or the CephFS kernel driver (Linux) for access. Measured in TB. | |||