Manage sandbox packages
This guide lists the sandbox packages in a silo, adds one, and changes the default.
A sandbox gets its size only from a package of kind sandbox. Every silo gets
sandbox-2g, sandbox-4g, and sandbox-8g, each with the trait sandbox=true.
Run every command on an operator workstation with a configured tritonadm.
List the packages in a silo
tritonadm silo package list <SILO>
Add a sandbox package
tritonadm silo package create <SILO> --name sandbox-16g --kind sandbox \
--cpu 8 --memory-bytes 17179869184 --disk-bytes 68719476736 --trait sandbox=true
--kind sandbox is required. The default kind is vm, and a VM package cannot size
a sandbox. Give the package the traits that your sandbox CNs carry, or no CN takes
it. See Place sandboxes with CN traits and labels.
A sandbox package may have at most 16 vCPUs, at most 64 GiB of memory in whole MiB, and a disk of 4 to 256 GiB in whole GiB.
Change a package
tritonadm silo package update takes the same flags as create. An update replaces
every field, so give each one again, including --kind sandbox, every --trait,
--group, and --description. --description defaults to an empty string.
An update makes a new package version. Existing sandboxes keep the version they were made with.
A seeded family that exists in any version is never seeded again, so your edit or retirement stays after a restart.
Change the default package
tritonadm config set sandbox.default_package sandbox-4g
A create that names no package uses this one, and the warm pool keeps the shape of
this package as the default silo defines it. The
setting applies at once. tritond checks only the name's format, so check that the
package exists in each silo first. A tenant whose silo has no such package gets a
400 that lists the packages it can use.
Changing the default package changes what the pool holds. Pool entries exist only on CNs whose traits take the new package, and each entry holds that package's memory in the CN's reservoir. A create takes an entry when its package has the same vCPUs, memory, and disk, so a same-sized package in another silo also uses the pool.
Check what a tenant sees
A tenant create that names a package it cannot use is refused with a 400 that lists
the packages it can use:
"<NAME>" is not a sandbox package you can use; choose a package: sandbox-2g, sandbox-4g, sandbox-8g
A create that gives sizes as numbers gets:
a sandbox is sized by a package, not by vcpus, memory_mib or disk_gib; choose a package: sandbox-2g, sandbox-4g, sandbox-8g
When the silo offers the tenant no sandbox package, both messages end with
no sandbox package is offered yet; ask your administrator in place of the list.
If a package name is taken
If a package of another kind already holds a seed name such as sandbox-2g,
tritond logs a warning, and sandboxes cannot use that name until you rename the
other package.