Connecting a node to the fabric

For a TurtiniOS node to appear in your fleet and host VMs, it joins the fabric — the registry every node advertises itself to. This is set at provisioning time.

Two things a node needs:
• The fabric address — where to publish itself (your Turtini's fabric endpoint).
• An enrollment token — a shared secret that authorizes the node to register. This keeps unknown machines from joining.

These are provided to the node as provisioning values (via your provisioning layer or a config drop-in on the machine) — they are never baked into the OS image, so no image carries a secret. Left unset, a node still runs, discovers peers on its local network, and keeps a local registry — it just doesn't publish to your central fabric.

Local discovery:
On a network, TurtiniOS nodes also find each other directly and mutually verify each other's identity before pooling into one fleet. A machine that fails verification is refused and never joins. So even without a central fabric, a set of nodes on the same network forms a trustworthy fleet.

Verifying it worked:
Open the Cloud module's Nodes tab. A newly joined node appears there within seconds, showing its role, hardware, and online status. Server nodes with virtualization also appear on the Hosts tab.