Administration overview

Stratum is run through the same interfaces its tenants use, with an admin area on top:

Interface	Address	Use it for
Console	http://<node>:8088	Everyday administration, under Admin.
stratumctl	the API	Scripts and the command line. Installed on the node.
API	http://<node>:8443	Everything; the console and the CLI are clients of it.
Terraform provider	the API	Tenant resources as code. It reads the same profile file as stratumctl.

With DNS forwarding in place (LAN access), the API also answers over TLS at https://stratum.<parent-domain>.

Single node or cluster

Everything here applies to both. Where a cluster differs, the page points to Manage a cluster; where a page is about a single node only, it says so.

Three layers

The console’s Admin area, and this section, follow the stack from the hardware up:

Layer	Is	Covers
Metal	The machines and their Linux host	Nodes, hardware and drive health, disks, maintenance, power, what each node runs.
Substrate	The platform’s own services	The control plane and what it depends on, readiness and settling, service health and logs, host reservation, upgrades, the platform backup.
Platform	What tenants get	Tenancy and quotas, identity, managed services, alarms, audit, networking, DNS, storage, images, compute, settings.

The instance agent, which runs inside tenant instances, has its own section.

The CLI in two commands

stratumctl configure --endpoint http://192.0.2.10:8443 --region local-1
stratumctl login --email admin@example.com

Settings live in ~/.stratum/config.yaml, one profile per install. Every command takes -o json, -o yaml or -o text, and --project for project-scoped calls. stratumctl <command> --help documents each command.

Two kinds of user

• Operators hold an install-wide role (platform-admin, or the bootstrap-admin the install creates). They manage the metal, the substrate and the platform.
• Tenants work inside projects: instances, networks, volumes, load balancers, DNS zones and backups, within quotas.