Skip to main content
POST
/
cloud
/
v3
/
gpu
/
virtual
/
{project_id}
/
{region_id}
/
clusters
Create virtual GPU cluster
curl --request POST \
  --url https://api.gcore.com/cloud/v3/gpu/virtual/{project_id}/{region_id}/clusters \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "flavor": "<string>",
  "name": "<string>",
  "servers_count": 123,
  "servers_settings": {
    "interfaces": [
      {
        "type": "<string>",
        "ip_family": "ipv4",
        "name": "<string>"
      }
    ],
    "volumes": [
      {
        "boot_index": 1,
        "name": "<string>",
        "size": 123,
        "source": "<string>",
        "type": "cold",
        "delete_on_termination": false,
        "tags": {}
      }
    ],
    "credentials": {
      "password": "<string>",
      "ssh_key_name": "<string>",
      "username": "<string>"
    },
    "security_groups": [
      "<string>"
    ],
    "user_data": "<string>"
  },
  "tags": {}
}
'
{
  "tasks": [
    "<string>"
  ]
}

Authorizations

​
Authorization
string
header
required

API key for authentication. Make sure to include the word apikey, followed by a single space and then your token. Example: apikey 1234$abcdef

Path Parameters

​
project_id
integer
required

Project ID

Example:

1

​
region_id
integer
required

Region ID

Example:

7

Body

application/json
​
flavor
string
required

Cluster flavor ID

Example:

"g3-ai-32-192-1500-l40s-48-1"

​
name
string
required

Cluster name

Maximum string length: 256
Example:

"gpu-cluster-1"

​
servers_count
integer
required

Number of servers in the cluster

Example:

3

​
servers_settings
ServerSettingsInputSerializer · object
required

Configuration settings for the servers in the cluster

​
tags
CreateTagsSerializer · object

Key-value tags to associate with the resource. A tag is a key-value pair that can be associated with a resource, enabling efficient filtering and grouping for better organization and management. Some tags are read-only and cannot be modified by the user. Tags are also integrated with cost reports, allowing cost data to be filtered based on tag keys or values.

Example:
{ "my-tag": "my-tag-value" }

Response

200 - application/json

OK

​
tasks
string[]
required

List of task IDs

Example:
["d478ae29-dedc-4869-82f0-96104425f565"]