nimmo/nixos-config
nimmo/nixos-config
Watch
1
0
Fork
You've already forked nixos-config
 0
Code Issues 15 Pull requests Wiki Activity Actions
Page: 11 Fleet Overview
Pages
00 Documentation Map and Scope 00 Documentation Standards 00 Start Here and Governance 10 System Atlas 11 Fleet Overview 12 Host Inventory 13 Service Catalogue 14 Network and Access Topology 15 Storage and Data Map 16 Automation and Control Plane 20 Architecture Decisions 21 ADR 001 Electra Hardware Specialisations 22 ADR 002 Workload Placement 23 ADR 003 Network Exposure 23 Project Tracking 24 ADR 004 Engram Durable Agent Memory 24 Security Baseline 25 ADR 005 Auto Update Control Plane 26 ADR 006 Scoped Secret Files 30 Operations and Runbooks 31 Routine Fleet Operations 32 Safe Testing and Deployment 33 Host Provisioning 34 Monitoring and Service Investigation 35 Backup Verification and Partial Restore 36 Full Host Recovery 37 Electra Boot Trust Recovery 38 Secret Editing and Recipient Rotation 39 Auto Update Incident Response 39a Service Migration and Cutover 39b Wrapper Repository Packaging 40 Engineering Handbook 41 Repository Structure and Import Chain 42 Configuration Ownership Boundaries 43 Adding Packages and Flake Inputs 44 Adding a Module or Profile 45 Adding a Host 46 Adding or Migrating a Service 47 Testing and CI Contracts 48 Secrets Implementation Conventions 49 Documentation Maintenance 50 NixOS Learning Path 51 Guided Repository Tour 52 Nix Language Essentials 53 Declarative Configuration Store and Generations 54 Flakes and Inputs 55 NixOS Modules and Option Merging 56 SpecialArgs and Home Manager Argument Flow 57 Electra Specialisations Worked Example 58 Nix Troubleshooting Primer 90 Historical Material 91 Electra Secure Boot Hardening Record Home
2 11 Fleet Overview
Nimmo edited this page 2026-09-12 11:57:20 +01:00
Table of contents

Fleet Overview

  • Type: Reference
  • Status: Current
  • Scope: Fleet
  • Canonical sources: flake.nix, hosts/*/default.nix, potential/nova/default.nix, and evaluated nixosConfig.host values
  • Last verified: Source commit 556df88494686003b1c4f20c8e0b99b5afc16a6e (2026-09-12); deployment evidence checked in Beszel on 2026-09-12
  • Review triggers: Changes to nixosConfigurations, potential/, host roles or locations, fleet networking, service placement, or deployment status

The managed fleet consists of two NixOS laptops, two physical NixOS servers, and two NixOS virtual machines. Nova has a staged configuration but is not a NixOS flake target and continues to run Fedora.

At a glance

Host Form Channel Role Location Nebula Configuration state
electra Framework 16 laptop Unstable Primary mobile workstation Mobile 10.10.0.20 Registered and deployed
lena Lenovo IdeaPad 5 2-in-1 laptop Unstable Claire's laptop Mobile 10.10.0.21 Registered and deployed
vega Physical Intel server Unstable Storage-backed services, AI agents, and cache Desk 10.10.0.2 Registered and deployed
lyra Physical Intel/NVIDIA server Unstable GPU compute and media services Desk, on top of Vega 10.10.0.3 Registered and deployed
cosmos Proxmox VM Stable 26.05 PostgreSQL and Adminer pve2 10.10.0.8 Registered and deployed
chaos Proxmox VM Stable 26.05 Container workloads unsuitable for native packaging pve2 10.10.0.9 Registered and deployed

Here, registered means present in flake.nix under nixosConfigurations. Deployed means the host has reported the matching NixOS family to Beszel; it does not claim that the host is currently online or at the latest repository revision. Availability is deliberately left to live monitoring rather than copied into this reference.

All six registered hosts are auto-update consumers. Electra, Lena, Vega, and Lyra evaluate from the unstable input; the database and container VMs use the stable NixOS and Home Manager inputs.

Staged host

Host Current operating system Intended role Repository state
nova Fedora 44 Framework Desktop with AMD GPU compute and the update-producer workload Configuration remains under potential/nova/; not registered in flake.nix

Nova's live operating system was verified through Beszel on 2026-09-12. Its staged NixOS file describes intended future behavior only and must not be used as evidence that NixOS services or commands are active there.

Major relationships

Internet clients
      |
      v
Pangolin ingress ---- TLS ----> Newt-connected service hosts
                                      |-- Vega: storage-backed web and AI services
                                      |-- Lyra: GPU/media services
                                      `-- Chaos: container workloads and Paseo web/relay

Nebula mesh
      |-- laptops and servers reach private service listeners and mesh DNS
      |-- Cosmos supplies mesh-only PostgreSQL and Adminer
      `-- Vega provides selected shared control-plane and resolver functions

Mass Storage NAS
      `-- shared media/application data ---> Vega and Lyra native services

This is an orientation map, not a port or service inventory. Detailed service, network, storage, and automation relationships belong in their respective System Atlas pages.

Boundaries

  • A flake target proves that a NixOS configuration can be evaluated; it does not prove current live deployment.
  • A service import or enable = true proves declared intent; live cutover state may still be transitional and must be stated explicitly in the Service Catalogue.
  • Beszel reports operational evidence at a point in time; it is not the source of declarative configuration.
  • Equipment outside this repository, including the NAS, Proxmox hosts, Pangolin infrastructure, and other monitored machines, appears only where it forms a dependency or trust boundary for the managed fleet.

See Host Inventory for host-specific capabilities, the Service Catalogue for workload ownership, the Network and Access Topology for traffic paths, and the System Atlas for the remaining reference pages.