Fleet Command Center: Master Architecture & Operational Guide
Target System: omni-yo-221 (Oracle Cloud Infrastructure Always Free AMD Instance)
Created: October 2026
Primary Purpose: Single-point-of-contact lightweight command center to manage, update, inspect, and SSH into a fleet of remote servers with zero idle memory overhead.
⚠️ CRITICAL NOTICE FOR FUTURE AI ASSISTANTS
READ THIS FIRST BEFORE PROPOSING OR INSTALLING SOFTWARE ON THIS SERVER:
- Hardware Ceiling: This is an Oracle Cloud
VM.Standard.E2.1.Microinstance:- Physical RAM: ~951 MiB total (with 1.0 GiB swap).
- Compute: 1 OCPU / 2 vCPUs (fractioned AMD EPYC 7551).
- Storage: 45 GB SSD.
- Anti-Bloat Mandate:
- DO NOT propose or install heavy containerized management suites (e.g., Cockpit, Portainer, heavy Node.js dashboards, Uptime Kuma, Linkwarden, or multiple Docker runtimes).
- This server routinely operates near ~500 MB memory. Stacking heavy runtimes triggers the Linux Out-Of-Memory (OOM) killer and freezes the server via disk swap thrashing.
- The Fleet System: Multi-server management is handled by a native, dependency-free Python CLI tool (
/usr/local/bin/fleet, aliased toc). Do not replace it with an external platform unless explicitly instructed by the user.- SSH & Keys: All remote server connections use the dedicated ed25519 keypair at
~/.ssh/id_ed25519. Do not overwrite or delete this key.
1. System Architecture Overview
+-----------------------------+
| Oracle Cloud VPS (1GB RAM) |
| Host: omni-yo-221 |
+--------------+--------------+
|
[/usr/local/bin/fleet]
(Python 3 Standard Lib)
|
+------------------------+------------------------+
| |
[Interactive Mode] [Batch Execution]
fzf + OpenSSH (Multiplexed) ThreadPoolExecutor (Parallel)
| |
+--------------+--------------+ +--------------+--------------+
| | | |
v v v v
[ Remote Server 1 ] [ Remote Server 2 ] [ Remote Server 1 ] [ Remote Server 2 ]
(Interactive Shell) (Interactive Shell) (apt update / cmd) (apt update / cmd)
Component Details
- CLI Executable:
/usr/local/bin/fleet(and symlinked/usr/local/bin/c) - Source Code:
/home/ubuntu/fleet.py - Inventory File:
~/.fleet/inventory.json - SSH Key:
~/.ssh/id_ed25519(public key:~/.ssh/id_ed25519.pub) - SSH Multiplexing Sockets:
~/.ssh/sockets/(configured in~/.ssh/config) - Idle RAM Consumption: 0.00 MB (process only runs when a command is invoked).
2. Command Reference for the Human Operator
2.1 Quick Shell Aliases
| Alias | Command | Purpose |
|---|---|---|
c |
fleet ssh |
Open interactive fuzzy menu to pick a server and log in |
c <name> |
fleet ssh <name> |
Instantly log into <name> |
fs |
fleet status |
Live parallel health table (RAM, Disk, Load, Uptime, Containers) |
fup |
fleet update |
Run sudo apt update && upgrade -y && autoremove -y across all servers in parallel |
fup <name> |
fleet update <name> |
Run full update and autoremove on a single server |
frun "<cmd>" |
fleet run "<cmd>" |
Run any bash command across all servers in parallel |
fleet logs <srv> |
fleet logs <srv> [unit] |
Stream live logs for a container or systemd unit |
| Web Dashboard | https://stateoftheshit.com |
Live dark-mode telemetry (RAM, Disk, Uptime, Containers) |
2.2 Adding and Managing Servers
Step 1: Copy Command Center Public Key to Remote Host
View this machine's public key anytime:
fleet pubkey
Key value:
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBGxf3wP7+lIpn0b7OLtuCjS98DW6dk97SjTVHsLeqKP fleet-command-center
Add this key into ~/.ssh/authorized_keys on your other servers.
Step 2: Add to Inventory
# Direct syntax:
fleet add <server_alias> <ip_or_host> [user] [port] [group]
# Examples:
fleet add prod-web 192.168.1.50 root 22 prod
fleet add backup-box 51.15.20.10 ubuntu 22 backups
# Or run interactively (prompts you step-by-step):
fleet add
Step 3: View or Remove Servers
fleet list # View all configured servers
fleet remove <name> # Remove a server from inventory
2.3 Interactive Server Jump
Type c or fleet:
1. An interactive fzf search menu appears showing your servers, usernames, IPs, and tags.
2. Fuzzy-type any part of the name (e.g. web, prod, 192).
3. Press Enter → You are immediately logged into that server.
2.4 Running Commands Across Your Fleet
# Check disk and RAM across all servers:
fleet run "df -h /; free -m"
# Check Docker status everywhere:
fleet run "systemctl is-active docker"
# Target a specific group/tag:
fleet run -g prod "tail -n 20 /var/log/nginx/error.log"
# Target a single server:
fleet run -s prod-web "uptime"
2.5 Fleet-Wide Package Updates
# Update every registered server at once:
fleet update
# Update a single server:
fleet update prod-web
Automatically detects Debian/Ubuntu (apt), RHEL/Fedora (dnf), and Arch (pacman).
2.6 Live Health Check Probe
fleet status
Produces a real-time, parallel summary:
NAME STATUS UPTIME LOAD MEMORY ROOT DISK
--------------------------------------------------------------------------------------------------
prod-web ONLINE up 21 days, 4 hours 0.14 0.09 0.05 410M/2048M 24G free (32% used)
backup-box ONLINE up 8 days, 12 hours 0.02 0.01 0.00 180M/1024M 120G free (40% used)
staging-1 OFFLINE - - - Connection timed out
3. Technical Implementation & Internals (For Future AI Chats)
If the user asks a future AI chat to extend, modify, or troubleshoot fleet:
3.1 Inventory Storage Schema
Location: /home/ubuntu/.fleet/inventory.json
{
"server_name": {
"host": "1.2.3.4",
"user": "root",
"port": 22,
"group": "prod",
"auth_type": "key"
}
}
3.2 SSH Performance Tuning
Location: /home/ubuntu/.ssh/config
Host *
StrictHostKeyChecking accept-new
ControlMaster auto
ControlPath ~/.ssh/sockets/%r@%h-%p
ControlPersist 10m
ServerAliveInterval 30
ServerAliveCountMax 3
IdentityFile ~/.ssh/id_ed25519
- Why ControlMaster? Sockets are kept in
~/.ssh/sockets/for 10 minutes. When running batch commands (fleet statusorfleet run), parallel connections reuse open TCP sockets without renegotiating SSH handshakes every time, speeding up execution by 500-1000%.
3.3 Extending the fleet CLI
- To modify or add functionality, edit
/home/ubuntu/fleet.py. - Copy the updated file to
/usr/local/bin/fleet:bash sudo cp /home/ubuntu/fleet.py /usr/local/bin/fleet sudo chmod +x /usr/local/bin/fleet - Rule: Do NOT introduce heavyweight third-party libraries (keep it pure standard library or use system tools like
fzf).