Skip to content

Server types

Server types are an important concept in MetalSoft. They are server ‘profiles’ or SKUs that users will operate on. A user will ‘ask’ for a specific ‘server_type’ and the system will match the exact server type if available or suggest an alternative.

MetalSoft also uses server types to verify a server’s registration. It performs the server_type-to-server match at register time.

MetalSoft auto-generates the label using the following:

{CLASS}.{CORES}.{RAM}[.{DISKS}][G][.v{VERSION}]
PartSourceNotes
CLASSserverClass enum → letterM
CORESprocessorCount × processorCoreCounttotal logical cores
RAMramGbytesinteger GB
DISKSdiskCountonly appended if > 0
GgpuCount > 0suffix, no dot
v{N}auto-incrementappended if label already exists (.v2, .v3, …)

Examples: M.16.64 → M.16.64.4 (with 4 disks) → M.16.64.4G (with GPU) → M.16.64.4G.v2 (duplicate)

This is typically not required, as MetalSoft creates server types automatically at server registration time. Click on a server and select the Add server type button.

Fill in the Server ID of the server you want to use as a template, click on Populate from server, fill in the other fields and click Create server type.

This is typically not required, as MetalSoft creates server types automatically at server registration time. If you need to change the server type, click on the server in the admin interface, click on Advanced, click on the Change server type button, and select the relevant server type.

Terminal window
curl "https://<your-server>/api/v2/server-types" \
-H "Authorization: Bearer <API_KEY>"
Terminal window
curl "https://<your-server>/api/v2/server-types/{serverTypeId}" \
-H "Authorization: Bearer <API_KEY>"
Terminal window
curl -X POST "https://<your-server>/api/v2/server-types/statistics" \
-H "Authorization: Bearer <API_KEY>"

Removes server types that are not assigned to any server:

Terminal window
curl -X POST "https://<your-server>/api/v2/server-types/actions/clean-unused" \
-H "Authorization: Bearer <API_KEY>"