Getting started with Aeolus
Install Aeolus from the CloudBSD package set, point at the docs, and bring up a first ensemble. Start small, then grow into mesh and HA when you need…
Operator notes
Aeolus Notes
Operator notes for the OCI runtime on CloudBSD
Read note: Getting started with Aeolus
Networking: ports and aliases
Publish the ports you need, give services stable names, and keep ensemble DNS inside the stack so containers find each other without hard-coded addresses. Networking features Published ports…
Volumes, mounts, and persistence
Containers come and go; data should not. Aeolus volumes and mounts keep databases, uploads, and config where you expect them after a restart. Persistence basics Named volumes —…
HA across nodes
The public Aeolus status panel shows an honest HA layout: multiple web, database, cache, and worker instances spread across nodes — not a single box pretending to be…
Resource limits with RCTL
Aeolus can apply resource controls that CloudBSD already understands — RCTL and related caps — so a noisy container does not starve the host. Honest limits Memory and…
Cluster mesh and public TLS
Cluster nodes talk to each other over a private mesh with mutual TLS. Public product names use Let’s Encrypt. Those are different trust domains on purpose. Two certificate…
Ensembles: multi-service stacks
An ensemble is a multi-service stack declared once and brought up together — web, database, cache, workers — with stable aliases instead of hunting IP addresses. Why ensembles…
What Aeolus is
Aeolus turns OCI container images into CloudBSD jails. The CLI shape will feel like home if you already live in containers — the runtime is jails, not a…