Introduction — Read This First
- What this book is
- Who it is for
- The thesis: you do not need to be a hyperscaler
- How to use this book
- The shape of the journey
- A method, not a product
Apache CloudStack — The Sovereign AI Factory
- On owning what you run
The Book in Full — Annotated Contents
- Part I — Build
- Part II — The Flex
- Part III — The Brains
- Part IV — Make It Pay
- Front and back matter
- The expanded edition
Chapter 1 — Why Own an AI Factory
- The Story: the second letter
- The thesis: you do not have to be a hyperscaler
- What this factory is — and what it is not
- The strongest reason: data that cannot leave the building
- The live hook: the week a model could be pulled
- GYOCYO: Grow Your Own, Cook Your Own
- Return on Research
- The Mars heuristic
- The map of the journey ahead
- The honesty contract
Chapter 2 — The Build of Materials
- The Story: counting what the building already holds
- How to read this bill of materials
- Tier 1 — The responsive tier: two Dell R7525s
- Tier 2 — The quality brain: two Dell R740XDs, 768GB each
- Tier 3 — The ARM model farm: one Ampere Ultra
- The graphics-card pool, counted honestly
- Tier 4 — The management plane: an R660, or a pair of Raspberry Pis
- Where these four tiers live: three clusters in one zone
- Proving the iron: a hardware-readiness pass
- What is not on the headline list — but you still need
- The shape of the cost — without a figure
Chapter 3 — Racking, Power and the Off-Grid Interlock
- The Story: four of a kind
- The rack as a machine with a shape
- Power is not a wall socket
- Measure the draw: a power-and-thermal readiness pass
- The factory that parks itself
- The off-grid interlock
- Every watt on purpose
Chapter 4 — Network Fabric: the Quad-25Gb Front-End, the Back-to-Back 100Gb, and Where CloudStack Ends
- The Story: the question on the wall
- Two fabrics, one estate
- The quad-25Gb front-end: the network CloudStack governs
- The back-to-back 100Gb: short, switchless, and honest about its shape
- Where CloudStack ends
- Bring up the fabric: a network-readiness pass
- Every wire on purpose
Chapter 5 — The Management Plane: the Conductor of the Estate, Built Two Honest Ways
- The Story: the conductor they already had
- What the conductor actually holds
- The caveat, stated plainly: one node is no HA
- Option A — the datacentre default: a Dell R660
- Option B — the low-power showcase: two Raspberry Pi 5s
- The HA aside: keepalived, HAProxy, and a replicated database
- A note on management traffic, and a warning about the keys
- Bring up the conductor — a management-node readiness pass
- The Mars test, applied to the conductor
- Built, not yet installed
Chapter 6 — CloudStack on the R7525s: KVM, and the GPU and NIC Made Schedulable
- The Story: the hosts that waited
- Installing against the conductor
- KVM on the R7525s
- A zone, a pod, a cluster
- Making the iron schedulable
- Bring the platform up — an install-and-passthrough readiness pass
- The Mars test, applied to the install
- An orchestra, ready to be told what to play
Chapter 7 — The Flex: Profiles A, B and C as Templates
- The Story: the cluster that left
- The template is the unit of the flex
- Switching is destroy-and-redeploy, not live-migrate
- Profile A — the four-node vLLM cluster
- Profile B — the two-node aggregated pair
- Profile C — four independent tenants
- Placement is your job, not the scheduler’s
- The flex as code
- Build the flex — a profiles-and-templates readiness pass
- Three machines, one rack
Chapter 8 — The RDMA Inference Fabric: RoCEv2 Reality-Checked, vLLM Across the Cluster
- The Story: the number nobody would say
- The link is RDMA, not merely a fast port
- The switchless pair is the easy case — say so
- The driver question: in-box first
- GPUDirect RDMA: assume it is not there
- vLLM across the pair: what distribution actually buys
- The measured reality: a method, not a number
- Build the fabric — an RDMA-and-vLLM readiness pass
- The fast wire, reckoned with
Chapter 9 — The Quality Brain: GLM-5.2 (and Kimi) on the 768GB R740XDs via llama.cpp
- The Story: the quiet join
- The tier, and why it is a separate machine
- Why this model: ownership you cannot have revoked
- What GLM-5.2 actually is
- The engine: llama.cpp, and the honest size problem
- How llama.cpp spends the one GPU
- Speed, told straight
- The line-up: one brain, or two, and which ones
- What this tier is for — and what it is emphatically not
- Settled, and VERIFY-on-live
- Build the brain — a quality-brain readiness pass
- The brain that answers the hard ones
Chapter 10 — The ARM Model Farm: Ampere Ultra, CPU-or-GPU
- The Story: the odd one in
- The tier nobody else covers
- Why ARM, on purpose
- The multi-architecture zone, made real
- CPU or GPU: the two ways this box serves
- The engines that run clean on arm64
- What this tier is for, and what it is not
- Settled, and VERIFY-on-live
- Build the farm — an ARM-farm readiness pass
- The third tier, in its place
Chapter 11 — Corpus and RAG: Retrieval Over Your Own Documents
- The Story: the one who asked what the data said
- Two ways to make a model know something
- The pipeline, end to end
- Ingest and chunk: cutting the corpus to size
- Embed: the second, smaller model
- Store: Qdrant, the vector index
- Retrieve and rerank: similarity is not relevance
- Ground: which brain answers, and from what
- What RAG is, and what it is not
- The sovereign half
- Build the pipeline — a RAG readiness pass
- Settled, and VERIFY-on-live
- The half that knows your documents
- The Story: a promise with a number waiting
Afterword - The estate is yours now
- About the author
- Stay in touch
Glossary
Appendix A — Bill of Materials
- The four tiers at a glance
- Tier 1 — Responsive / flex compute: Dell PowerEdge R7525 (×2)
- Tier 2 — Quality brain: Dell PowerEdge R740XD (×2)
- Tier 3 — ARM model farm: Ampere Ultra workstation (×1)
- Tier 4 — Management: two documented options
- The RDMA fabric
- On power and cooling