Fleet Orchestration

Build and operate a controller-driven Linux Fleet using SSH trust, Ansible inventory, verification, auditing and distributed tasks.

Fleet is the orchestration layer for managing multiple Linux systems as one operational estate. The controller owns inventory, trust and orchestration state; member nodes do not need a permanent inbound web management surface.

Initialise and Add Nodes

one-click fleet init
one-click fleet add <ip> <hostname> [port]
one-click fleet list
one-click fleet verify

Registration and verification are separate concerns. A host should not be considered usable merely because an address exists in a ledger; inventory, trust and successful controller reachability all matter.

Distributed Operations

one-click fleet audit
one-click fleet bench
one-click fleet update
one-click fleet update-keys
one-click fleet put <host> <src> <dest>
one-click fleet get <host> <src> <dest>
one-click fleet raw <host> "<command>"

Site Movement Inside a Trusted Fleet

one-click clone-site example.com peer-node
one-click restore-site example.com peer-node

Use peer cloning/restoration when both sides are already under the same trusted Fleet controller. Use the external import/export workflow when crossing that Fleet boundary.

Fleet Security Model

• SSH key-based controller trust.
• Reduced inbound exposure on managed nodes.
• Controller-driven automation rather than shared passwords.
• Explicit onboarding and offboarding of infrastructure.

If a Managed VPS Is Missing

Fleet inventory and VPS registration are distinct from a hypervisor being reachable. If a host appears but its guests do not, check that the guest is recorded and associated with the correct hypervisor before assuming the Fleet listing is broken. Confirm the change before running migrations or backups.