Compute

Nodes

Machines that can be given work. A node is online because its agent heartbeated, not because it was created — so a node you have just added will sit at provisioning until it runs the bootstrap, and a node whose agent has stopped will read offline about 45 seconds after its last heartbeat even though the stored status still says online.

A node belongs to exactly one organization, so there is nowhere to put this one until an organization exists. An organization is the outermost boundary in the system: everything else lives inside one.

Go to organizations and create one Open the organizations screen

Add a node

This produces a one-line command and a six-digit code. Run the command on the machine; it asks for the code, pairs with the controller, installs the agent and registers it as a service.

Organization A node belongs to exactly one organization, so the node list and every job it takes are scoped by it. A platform administrator has no organization of their own and must choose one — that is why this is a field rather than something inferred.

Node name The name this machine will report. The pairing code is bound to it, so a code that ends up in the wrong hands cannot pair a different machine. Lowercase letters, digits and dashes read best on a terminal.

Where it is For you, not for the system. Helps when six nodes report at once.

Trust domain Used to refuse work across a boundary you have said is a boundary.

Controller address The address the node will reach us on, from the node's side. If the node is on another machine, use an address it can resolve.

Expect to run as root on an exclusive machine Ticking this changes the command below to curl … | sudo sh and installs to /opt/umbra as a system service running as its own umbra-node account. Unticked, everything stays in your home directory with a user service and no password is needed.

The account running the command must be in the sudo group. On a machine set up with a separate administrator and then a daily-use account, the first account created is the one that gets sudo; a later account does not. Check with id -nG. If sudo is not listed, an administrator adds it: sudo usermod -aG sudo account then sign out and back in — group membership is fixed at sign-in.
To avoid typing a password for every node, grant passwordless sudo for that one account. Run this from an account that already has sudo: sudo visudo -f /etc/sudoers.d/umbra-node then add this line and save: umbra ALL=(ALL) NOPASSWD: ALL Replace umbra with whichever account will run the command. Without this step the command still works — it will simply ask for a password each time.

Nodes

Add a node

Run this on the machine