Key concepts and technical specifications
Technical specifications
Bare Metal Flavors
NVIDIA™ H100 SXM and A100 SXM
H100.8GPU.4NV | H100.8GPU.4NV | A100.8GPU.6NV | |
GPUs | 8 GPUs | 8 GPUs | 8 GPUs |
Total VRAM | 640 GB | 640 GB | 640 GB |
vCPUs | 112 vCPUs | 64 vCPUs | 128 vCPUs |
Memory | 2000 GB RAM | 2000 GB RAM | 1000 GB RAM |
Block Storage | 4000 GB | 4000 GB | 4000 GB |
Shared Storage | NFS, various volume | NFS, various volume | NFS, various volume |
Internal Network | 2x 25 Gbps | 2x 25 Gbps | 2x 25 Gbps |
North-South Speed | Up to 100 Gbps | Up to 100 Gbps | Up to 100 Gbps |
Infiniband | 8x 400 Gbps | 8x 400 Gbps | 8x 200 Gbps |
NVLink Support | yes (up to 900GB/s) | yes (up to 900GB/s) | yes (up to 600GB/s) |
Virtual Machine Flavors
NVIDIA™ A100 SXM
A100.1GPU | A100.2GPU | A100.4GPU | A100.8GPU | A100.8GPU.6NV | |
GPUs | 1 GPU | 2 GPUs | 4 GPUs | 8 GPUs | 8 GPUs |
Total VRAM | 80 GB | 160 GB | 320 GB | 640 GB | 640 GB |
vCPUs | 16 vCPUs | 32 vCPUs | 64 vCPUs | 128 vCPUs | 128 vCPUs |
Memory | 125 GB RAM | 250 GB RAM | 500 GB RAM | 1000 GB RAM | 1000 GB RAM |
Block Storage | 500 GB | 1000 GB | 2000 GB | 4000 GB | 4000 GB |
Shared Storage | - | - | - | - | - |
Internal Network | Up to 2x 25 Gbps | Up to 2x 25 Gbps | Up to 2x 25 Gbps | 2x 25 Gbps | 2x 25 Gbps |
North-South Speed | Up to 100 Gbps | Up to 100 Gbps | Up 100 to Gbps | Up to 100 Gbps | Up to 100 Gbps |
Infiniband | - | - | - | - | - |
NVLink Support | - | - | - | - | yes (up to 600GB/s) |
Virtual Machine Flavors
NVIDIA™ RTX A6000
RTXA6000.1GPU | RTXA6000.2GPU | RTXA6000.4GPU | |
GPUs | 1 GPU | 2 GPUs | 4 GPUs |
Total VRAM | 48 GB | 96 GB | 192 GB |
vCPUs | 6 vCPUs | 12 vCPUs | 24 vCPUs |
Memory | 55 GB RAM | 110 GB RAM | 220 GB RAM |
Block Storage | 500 GB | 1000 GB | 2000 GB |
Shared Storage | - | - | - |
Internal Network speed | Up to 2x 25 Gbps | Up to 2x 25 Gbps | 2x 25 Gbps |
North-South Speed | 10 Gbps | 10 Gbps | 10 Gbps |
Infiniband | - | - | - |
NVLink Support | - | - | - |
Concepts
Our service relies on a few organizing concepts:
Tenant: The customer receives a tenant to create accounts and manage resources. Virtual Machines (VM) consumption is tracked by tenant.
Account: Accounts are associated with a tenant and allow its users to authenticate to the cloud platform to create, access and delete cloud resources.
Network: A network contains the IPv6 address spaces for your VMs.
Cluster: Clusters reflect our datacenters. A6000 clusters are currently located in Norway, A100 clusters in Sweden.
Bare Metal Instance (BM): A BM offers non-virtualised access to the high-performance computing server located in our datacenters, and offers a full set of computing resources on that server based on a flavor.
Virtual machine (VM): A VM represents a virtualized slice of the high-performance computing servers located in our datacenters, and offers a specific set of computing resources based on a flavor.
Flavor: A flavors is a pre-defined configuration of computing resources (GPUs, vCPUs, RAM, Storage) which we offer with our VMs.
Image: VMs are initialized with an image of an operating system.
UUID: Universally unique identifiers (UUIDs) are 128-bit labels to globally identify resources on the platform. All instances (e.g., tenants, accounts, or VMs) have individual uuids.
Basic usage
Each item in a response has a so-called uuid. The uuid is a unique identifier of an item which must be entered in an API call so the system understands which item to process. For example, to boot your VM with an Ubuntu 22.04 LTS operating system, enter the uuid of this image in the appropriate field of the POST /vm/vms
API call.
If you want to get more information about a certain object (e.g. of the Ubuntu 22.04 LTS OS image), simply use one of the Info calls. That’s the response of the GET /info/images
API call:
Understanding the API info call
There is one call that returns information about all the components that are required to start a VM - the GET /info
API call. It is the baseline of this API.
The tenant is the most important item as it is required to create all components of a VM. Tenants are listed under customer_info in the response. Please make sure that the tenant uuid is consistent throughout all the components of a VM, such as ssh-key, network, IPv4 address and the VM itself!
{
"images": [{
"uuid": "string",
"name": "string",
"size": 0}],
"flavors": [{
"uuid": "string",
"name": "string",
"slug": "string",
"cpu_type": "string",
"core_count": 0,
"ram": 0,
"storage_size": 0,
"gpu_type": "string",
"gpu_count": 0,
"available": false}],
"customer_info": [{
"uuid": "string",
"customer_name": "string",
"username": "user@example.com"}],
[…]
GET /info excerpt (default response)