oz0 tenant region
For: Operators and developers looking up a command.
Show the region a tenant is pinned to: its jobs run only on that region's nodes, through that region's edges; its Temporal histories are on that region's backend and its payloads in that region's payload store; and its model calls go only to providers in that region unless its data rules name other regions.
--set moves the tenant to another region ("" for the unnamed region): its new work goes there at once, while its running jobs finish in the old region, whose edges then serve nothing else of it. Nothing is copied: its closed histories and payloads stay in the old region until that region's retention removes them, so export the tenant first if you need them.
A node joins only in its tenant's region: join the tenant's nodes through the new region's edges once the move started; its new jobs wait there until one runs. The move ends once nothing of the tenant runs in the old region; --wait waits for that. Moving takes a cluster admin and --reason (or $OZ0_REASON), which the audit log keeps.
Usage
oz0 tenant region <tenant> [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--json | bool | print JSON instead of a table | |
--reason | string | why, required for a move (default $OZ0_REASON); the audit log keeps it | |
--set | string | move the tenant to this region | |
--wait | duration | with --set: wait this long for the move to end |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.