Boat managed machines
Do you need one?
Use a managed VM only when the work needs dedicated CPU/RAM (parallel builds,
big test suites, memory-hungry Lean/Rust) or isolation, or when
get_compute_fleet shows no free capacity. Reading code, reviews and short
probes run where you are.
Size
All sizes run the same CPU: AMD Ryzen 9 9950X (Zen 5, AVX-512, VPCLMULQDQ).
Size buys cores and RAM, not CPU features. Do not rent xlarge to check CPU
flags.
| size |
vCPU / RAM |
$/h |
use for |
| small |
2 / 4 GB |
0.018 |
probes, audits, single tests |
| default |
4 / 8 GB |
0.036 |
normal builds |
| large |
8 / 16 GB |
0.072 |
parallel cargo/lake builds |
| xlarge |
16 / 32 GB |
0.20 |
only measured heavy fan-out |
TTL defaults to 60 min and auto-extends in 30 min steps while the VM is busy.
Do not ask for long TTLs.
Budget
Call get_budget first. If your mission has a pool, every VM, extension,
fork and resume is checked against it (budget_exceeded says what is
left). Give a child its own cap with start_mission(..., budget_usd=2); it
must fit your remaining pool.
One warm snapshot per project
Set up once, then start children from it:
spawn_managed_machine(size="large", reason="warm image")
- On it: clone the repos, install the pinned toolchains, run the builds that
fill caches. Keep everything outside
/tmp and ~/.cache: snapshots do
not keep them. Use e.g. /var/lib/orb-node/work/<repo>, CARGO_TARGET_DIR
and .lake inside the repo.
snapshot_managed_machine(machine_id="large-a", name="lean-native-warm"),
then poll list_managed_snapshots() until ready.
- Children: Boat VMs boot in light mode (clean
orb-node-base, no snapshot
files) by default unless you pass a snapshot explicitly:
start_mission(remote_node_id="auto-managed:default", managed_from_snapshot="lean-native-warm", ...) or
spawn_managed_machine(from_snapshot="lean-native-warm").
Refresh the snapshot when lockfiles or toolchains change (same name, then
delete the old one). Core keeps the newest 2 per project and deletes ones
unused for 14 days; 10 are free, then $1.70/month each.
Fork when a child needs your exact state
fork_managed_machine(machine_id="large-a") copies your VM for one child,
then start_mission(remote_node_id="<returned name>", ...). Boat forks from
a background snapshot up to about a minute old: write and sync what the
child needs and wait ~60 s, or take a named snapshot for an exact copy.
Share one VM between sequential siblings
If children run one after another, rent one VM yourself
(spawn_managed_machine) and start each child on it by name. You stay the
owner, so the VM survives each child. auto-managed also reuses an idle VM
of the same size left by an ended sibling.
Stop instead of idling, destroy when done
- Pausing for a while (waiting on review, CI, the user):
stop_managed_machine(machine_id=...), later
resume_managed_machine(machine_id=...) (same name, files kept, processes
restart; within 24 h). The reaper also stops VMs of interrupted or waiting
owners and resumes them when the owner works again.
- Finished:
destroy_managed_machine(machine_id=...).
list_managed_machines() shows what you own (compact; verbose=true for
everything).
Credentials
VMs hold no credentials. git over https to github.com uses the GitHub token
Core delivers to your mission; never paste tokens into commands or files.
1---2name: boat-machines3description: "When and how a mission should rent boat.dev managed VMs: whether to use one at all, size choice, one warm snapshot per project, forking the parent VM, sharing a VM between sequential siblings, stopping instead of idling, budgets and cleanup. Use before spawn_managed_machine, start_mission(remote_node_id=\"auto-managed:...\"), fork, snapshot or stop/resume tools."4license: MIT5metadata:6 source: https://skillmd.com/skills/th0rgal/boat-machines7 hermes:8 tags: [Boat, Managed-VM, Compute, Budget, Snapshot]9 related_skills: [sandboxed-sh-missions]10---1112# Boat managed machines1314## Do you need one?1516Use a managed VM only when the work needs dedicated CPU/RAM (parallel builds,17big test suites, memory-hungry Lean/Rust) or isolation, or when18`get_compute_fleet` shows no free capacity. Reading code, reviews and short19probes run where you are.2021## Size2223All sizes run the same CPU: AMD Ryzen 9 9950X (Zen 5, AVX-512, VPCLMULQDQ).24Size buys cores and RAM, not CPU features. Do not rent `xlarge` to check CPU25flags.2627| size | vCPU / RAM | $/h | use for |28| --- | --- | --- | --- |29| small | 2 / 4 GB | 0.018 | probes, audits, single tests |30| default | 4 / 8 GB | 0.036 | normal builds |31| large | 8 / 16 GB | 0.072 | parallel cargo/lake builds |32| xlarge | 16 / 32 GB | 0.20 | only measured heavy fan-out |3334TTL defaults to 60 min and auto-extends in 30 min steps while the VM is busy.35Do not ask for long TTLs.3637## Budget3839Call `get_budget` first. If your mission has a pool, every VM, extension,40fork and resume is checked against it (`budget_exceeded` says what is41left). Give a child its own cap with `start_mission(..., budget_usd=2)`; it42must fit your remaining pool.4344## One warm snapshot per project4546Set up once, then start children from it:47481. `spawn_managed_machine(size="large", reason="warm image")`492. On it: clone the repos, install the pinned toolchains, run the builds that50 fill caches. Keep everything outside `/tmp` and `~/.cache`: snapshots do51 not keep them. Use e.g. `/var/lib/orb-node/work/<repo>`, `CARGO_TARGET_DIR`52 and `.lake` inside the repo.533. `snapshot_managed_machine(machine_id="large-a", name="lean-native-warm")`,54 then poll `list_managed_snapshots()` until `ready`.554. Children: Boat VMs boot in light mode (clean `orb-node-base`, no snapshot56 files) by default unless you pass a snapshot explicitly:57 `start_mission(remote_node_id="auto-managed:default",58 managed_from_snapshot="lean-native-warm", ...)` or59 `spawn_managed_machine(from_snapshot="lean-native-warm")`.6061Refresh the snapshot when lockfiles or toolchains change (same name, then62delete the old one). Core keeps the newest 2 per project and deletes ones63unused for 14 days; 10 are free, then $1.70/month each.6465## Fork when a child needs your exact state6667`fork_managed_machine(machine_id="large-a")` copies your VM for one child,68then `start_mission(remote_node_id="<returned name>", ...)`. Boat forks from69a background snapshot up to about a minute old: write and `sync` what the70child needs and wait ~60 s, or take a named snapshot for an exact copy.7172## Share one VM between sequential siblings7374If children run one after another, rent one VM yourself75(`spawn_managed_machine`) and start each child on it by name. You stay the76owner, so the VM survives each child. `auto-managed` also reuses an idle VM77of the same size left by an ended sibling.7879## Stop instead of idling, destroy when done8081- Pausing for a while (waiting on review, CI, the user):82 `stop_managed_machine(machine_id=...)`, later83 `resume_managed_machine(machine_id=...)` (same name, files kept, processes84 restart; within 24 h). The reaper also stops VMs of interrupted or waiting85 owners and resumes them when the owner works again.86- Finished: `destroy_managed_machine(machine_id=...)`.87- `list_managed_machines()` shows what you own (compact; `verbose=true` for88 everything).8990## Credentials9192VMs hold no credentials. git over https to github.com uses the GitHub token93Core delivers to your mission; never paste tokens into commands or files.