Appearance
VMs
VMs (virtual machines) are the hosts that run the game servers RustyThrones hosts. This page registers them, shows how loaded they are and decides which ones may receive a new server. Capability: operations. This page describes what the screens do.
The list
The header reads "Hosts that run game servers." with "N of M online" and the number degraded or offline. Refresh reloads, Add VM opens the form. Each card shows:
| Part | Content |
|---|---|
| Header | Name, region, status chip, and a menu: Manage VM, Health check. |
| Rings | CPU, RAM, Disk usage; amber above 70%, red above 90%. |
| Slots | Servers on the VM out of its maximum. |
| Reserved | Share of the VM's memory reserved by the servers on it. |
| Schedulable switch | When off, the VM is "inventory only": the automatic placement never chooses it. |
| Servers | The servers deployed on the VM. |
| Footer | Uptime, number of containers, time of the last health check. |
Status
The platform checks every VM about once a minute (CPU is not part of the status).
| Status | Meaning |
|---|---|
| online | Reachable, memory and disk under 80%. |
| degraded | Memory or disk at 80% or more. |
| critical | Memory or disk at 90% or more. |
| offline | The check could not reach the VM. |
| provisioning | Being prepared (bootstrap running). |
| unknown | Not checked yet. |
Add a VM
- Click Add VM.
- Identity: Name (required, up to 64 characters), Hostname (an address or domain, required), Region (free text), Max servers (1 to 50).
- SSH: User, Port and Private key (paste it, or Upload key file). The key is stored securely and never shown again.
- Optional Notes.
- Test connection (appears once the hostname and key are filled in) confirms the platform can log in.
- Add VM.
On the VM's page, Bootstrap shows Bootstrapped, Provisioning, Failed (View error) or "Not bootstrapped". The run-again button re-runs the bootstrap (Docker, network, directories); Retry Bootstrap is in the error dialog.
A VM's page
Sections Resources (rings, uptime, containers), Connection (hostname, SSH user and port, region, bootstrap), Capacity (servers out of the maximum, notes) and Deployed servers (each opens the server). Edit changes the name, region, maximum and notes. Health check refreshes the numbers now. The trash icon deletes the VM after confirmation; it is refused while servers are assigned ("Cannot delete VM with N assigned server(s). Remove servers first.").
Automatic placement
When a hosted request is approved with Automatic (VM scheduler), the platform picks the VM with the most free memory (ties go to the VM with fewest servers) among eligible VMs:
| Condition | Message when not met |
|---|---|
| Online | "Offline" / "Not online (status)" |
| Bootstrapped | "Not bootstrapped" |
| Schedulable on | "Not schedulable" |
| Fresh metrics (under 10 minutes) | "No metrics yet" / "Metrics stale" |
| A free slot | "Full: N/M" |
| Enough free memory for the requested size after a safety margin | "Needs X GB, Y GB free" |
The reasons are shown when approving, so you know why a VM is skipped. A named VM can still be chosen manually.
Troubleshooting
| Problem | Fix |
|---|---|
| Test connection fails | Check hostname, port, user and key; the VM must accept SSH from the platform. |
| VM stays offline | Fix reachability, then Health check. |
| Bootstrap Failed | Open View error, fix the cause, Retry Bootstrap. |
| Automatic placement unavailable | Needs the scheduler enabled and one eligible VM; pick a VM by name. |