Fork a new VM from a snapshot
Creates a VM from a snapshot, taking its GPU model and count, image, env vars, port and the source VM's SSH keys unless the request overrides them. The disk is never smaller than the snapshot's, and an unnamed fork is called fork-<snapshot name>. A valid request with no free capacity answers 503. The response carries the new VM's id, name and status.
Required permission
Requires the compute.create permission. See Permissions for the roles and API key permissions that include it.
Command line
The orl CLI wraps this endpoint:
orl vms fork --snapshot-id <snapshot-id>apiKeyAuthorizationBearer <token>OpenRelay API key. Send it as Authorization: Bearer or_… (legacy vl_… keys still work).
orgId*stringapplication/json- body
snapshotId*stringname?stringgpuModelId?stringlength <= 256gpuCount?integerresourceSize?stringdiskSizeGb?integerimageUrl?stringenvVars?containerPort?integersshKeyIds?array<string>Org SSH key ids for the fork. Omit to carry the source VM's keys over. Every resulting id must name a live key of this org, so forking a source whose keys are gone requires naming a replacement set here.
1 <= items <= 64Created
application/json- response
id*stringname*stringstatus*stringcurl -X POST 'https://api.openrelay.inc/v1/orgs/string/vms/fork' \ -H 'Content-Type: application/json' \ -d '{ "snapshotId": "string"}'{ "id": "string", "name": "string", "status": "string"}Soft-delete a snapshot DELETE
Soft-deletes a snapshot: its status becomes deleting, deletedAt is set and the call answers 204. A snapshot that is already being deleted answers 409.
Overview
Org-level SSH public keys that can be attached to VMs. Add a key and the server computes its fingerprint; list the org's keys or delete one.