Skip to main content

tritonadm cn sandbox

tritonadm cn sandbox sets a compute node's sandbox override. Each field has a cluster default, and the per-node value wins. There are two commands, set and clear. There is no show: the output of set shows the effective values.

Execution context​

Every command is an HTTP call against tritond, from any host with a configured tritonadm. <CN> is a hostname, UUID, or UUID prefix.

The compute node's agent reads these values when it starts. After a change, restart the agent on that CN:

tritonadm cn exec <CN> -- svcadm restart tritonagent

Both commands print that line on stderr as a reminder.

Synopsis​

tritonadm cn sandbox set <CN> [--enabled <BOOL>] [--max <N>] [--reservoir-percent <F>]
tritonadm cn sandbox clear <CN>

tritonadm cn sandbox set​

Replaces the whole override. A flag you leave out goes back to the cluster default.

OptionTypeCluster defaultDescription
--enabled <BOOL>true, falsesandbox.enabled_default, falseTake sandbox jobs on this CN.
--max <N>1 to 50sandbox.max_per_node_default, 50Sandboxes this CN runs at once, pool entries included. 0 is refused: use --enabled false.
--reservoir-percent <F>0.0 to 1.0sandbox.reservoir_percent_default, 0.25Share of physical memory held in the bhyve reservoir for sandbox guests.

The output prints each field as its value or (inherit), then one effective: line with enabled, max, and reservoir_percent.

Server errors name the field, for example max_per_node must be 1 to 50 or reservoir_percent must be a fraction from 0.0 to 1.0.

tritonadm cn sandbox clear​

Removes the override. The CN goes back to the cluster defaults for all three fields.

Local overrides in agent.env​

These lines in /opt/triton/tritonagent/etc/agent.env win over tritonadm on that CN, and the agent logs a warning for each one at start:

VariableOverrides
TRITONAGENT_ENABLE_SANDBOXES--enabled
TRITONAGENT_MAX_SANDBOXES--max
TRITONAGENT_SANDBOX_RESERVOIR_PERCENT--reservoir-percent
TRITONAGENT_ENABLE_RESERVOIRcn reservoir set --enabled
TRITONAGENT_RESERVOIR_PERCENTcn reservoir set --percent

Remove them so tritonadm controls the CN.

Reservoir interaction​

A sandbox CN manages its bhyve reservoir with no extra step, and holds it at the sandbox share. It does not apply the general reservoir floor from tritonadm cn reservoir set --percent. If tritonadm cn reservoir set <CN> --enabled false turns reservoir management off, every sandbox create on that CN is refused. A sandbox CN with no reservoir override follows reservoir.enabled_default, so setting that to false refuses sandbox creates on every such CN.

See also​