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.
LibreInfra Field Notes
Field Notes
Readable notes about architecture, operations, ownership and transfer.
All Field Notes
Showing 1-15 of 22 articles. Page 1 of 2.
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.
Edge infrastructure must survive the loss of the centre
A LibreInfra field note on edge autonomy, local identity, store-and-forward integrity, updates and recovery.
Infrastructure as code is only as ownable as its state
A LibreInfra field note on infrastructure-as-code state, provider versions, drift, execution authority and recovery.
Kubernetes is an orchestration engine, not an operating model
A LibreInfra field note on treating Kubernetes as one control plane inside a wider platform contract.
AI agents are infrastructure identities, not assistants with tools
A LibreInfra field note on governing AI agents as delegated infrastructure identities with bounded permissions, memory, tools, budgets and evidence.
Digital sovereignty is the ability to change course
A LibreInfra field note on digital sovereignty across authority, data, identity, operations, interoperability, open source and exit capacity.
Sustainable infrastructure begins with deciding what should not run
A LibreInfra field note on infrastructure sustainability, demand, useful work, data retention, hardware lifecycle, location and AI workload classes.
Open source without maintenance is borrowed infrastructure
A LibreInfra field note on open-source maintenance, dependency graphs, stewardship, contribution, forks and operational continuity.
Open weights do not make AI infrastructure ownable
A LibreInfra field note on open weights, rights, runtime, evaluation, organisational data, recovery and AI service ownership.
Observability should produce evidence, not just dashboards
A LibreInfra field note on observability as evidence: control-plane events, recovery records, alerts, retention and incident reconstruction.
Automation that cannot be transferred is another dependency
A LibreInfra field note on automation ownership, transferability, state, credentials, failure behaviour and operational evidence.
