oz0 region name
For: Operators and developers looking up a command.
Give the unnamed region a name, for a cluster that starts to use regions: every tenant and node that is in no region moves to <region> at once. Start the edges with --region <region> too, before or after: while the names differ, those tenants' work waits (Temporal keeps it; nothing is lost). Refused when tenants are pinned to that name already, and while a region move drains. Takes a cluster admin and --reason (or $OZ0_REASON).
Naming the region pins its tenants, and a pinned tenant whose data rules name no region may call only model providers in its region: a provider in another region, or one whose record names no region, is refused from then on, in running jobs too. Run with --dry-run first: it lists, per tenant, the providers and aliases that would be refused, and changes nothing.
Then set the tenants' rules (oz0 model rules --tenant <t> --region <regions>) or say where a provider runs (oz0 provider set <id> --region <region>) before you name the region.
Usage
oz0 region name <region> [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--dry-run | bool | say what naming the region would do, including the model calls its tenants would lose, and change nothing | |
--json | bool | print JSON instead of a table | |
--reason | string | why, required (default $OZ0_REASON); the audit log keeps it |
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.