Decisions

Short records of why things are the way they are.

• 0001 · Incus-first runtime and control-plane boundariesWhy Apelora runs modules on Incus and keeps its own control plane to application state.
• 0002 · Bare-metal provisioning through MAASWhy new servers are discovered and installed through MAAS.
• 0003 · Two Incus identities; members join with single-use tokensWhy Apelora uses two Incus identities and single-use join tokens.
• 0004 · Service discovery: stable addresses, delivered as environment; DNS optional laterWhy modules find each other through stable addresses delivered as settings, and DNS comes later.
• 0005 · Access model: roles bound to scopes, applications owned by projectsWhy roles are bound to scopes and applications are owned by projects.
• 0006 · The parts of an application are called modulesWhy the parts of an application are called modules.
• 0007 · Sign-in methods: identity providers, local accounts and a directoryWhy sign-in offers identity providers, local accounts and a directory.
• 0008 · Sectors: linking Incus clusters into one fabricWhy several Incus clusters are linked as sectors rather than made one large cluster.
• 0009 · A global fabric: regions, sites and sectors, with a control plane per regionRegions, sites and sectors, with a control plane for each region.
• 0010 · Installations without internet access (air-gapped and disconnected)Why Apelora supports installations without internet access.
• 0011 · One design at every size: same mechanisms from three servers to the global fabricWhy the same mechanisms serve three servers and a global fabric.
• 0012 · Environments own restricted Incus projects that Apelora prepares; quotas are Apelora's, mirrored as Incus limitsWhy each environment owns a restricted Incus project that Apelora prepares.
• 0013 · Fencing before a module restarts on another serverWhy a module restarts on another server only after its failed server is fenced.
• 0014 · Fencing by switching a server off through its BMCFencing a failed server by switching it off through its management controller.
• 0015 · Application lifecycle verbs: Shut down, Stop, and MigrateWhy an application has Shut down, Stop and Migrate beside Start and Restart, and what each does.