Self-owned infrastructure should be recoverable by someone who did not build it
A LibreInfra field note on operating records, reconstruction order, restore exercises, transfer tests and organisational recovery authority.
LibreInfra Field Notes
Field Notes
Readable notes about architecture, operations, ownership and transfer.
All Field Notes
Showing 1-15 of 32 articles. Page 1 of 3.
The management network is the part of the lab that must never be improvised
A LibreInfra field note on separating administrative authority, VPN access, identity, BMCs, DNS, certificates and operational evidence.
Storage is where a mini lab becomes real infrastructure
A LibreInfra field note on live storage, checksums, redundancy, application consistency, independent backup and tested restoration.
One strong server or three modest nodes? Choose the failure model first
A LibreInfra field note on selecting one host, two nodes or a three-node cluster from authority, capacity, state and recovery requirements.
A mini lab is not a miniature data centre
A LibreInfra field note on choosing a compact, understandable and recoverable platform around the organisational capabilities that matter.
An LLM strategy is a dependency and governance map
A LibreInfra field note on mapping LLM purpose, dependencies, governance, evaluation, sustainability, recovery and exit.
Companies do not deploy a model; they build an LLM system
A LibreInfra field note on enterprise LLM operating models, gateways, identity, retrieval, evaluation, monitoring and ownership.
What LLMs are useful for—and when not to use one
A LibreInfra field note on matching LLMs to language transformation, drafting, coding and bounded decision-support tasks.
How an LLM turns a prompt into an answer
A LibreInfra field note tracing the path from context assembly and tokenisation to generation, retrieval, tool use and verification.
A large language model predicts language—and that is more powerful than it sounds
A LibreInfra field note on tokens, Transformers, pretraining, instruction tuning, model knowledge and answer-time reasoning.
A server fleet is a power, cooling, firmware and spare-parts system
A LibreInfra field note on physical infrastructure control planes, BMCs, firmware baselines, spares and hardware recovery.
GPUs run LLMs because memory movement is the real workload
A LibreInfra field note on accelerator sizing for LLM inference, memory capacity, KV cache, interconnect and software support.
The R730 generation is still useful—inside a deliberate boundary
A LibreInfra field note on using R730-class hardware responsibly for labs, backup targets and recoverable internal platforms.
A server type is a workload decision, not a chassis preference
A LibreInfra field note on choosing server types from workload shape, serviceability, power, cooling and failure boundaries.
A historian, a broker and a data lake are different systems
A LibreInfra field note on brokers, historians, data lakes, archives, time, asset identity and recovery contracts.
