Design notes

How individual features were designed, with their evidence.

• Deploying an application from the StudioHow a design becomes running instances: plan, approve, jobs and live status.
• Applications view: create an application, open its canvasThe Applications list: creating an application, opening its canvas, and its lifecycle.
• Application-level readinessDeciding that an application is ready from more than a port check.
• Health and capacityThe Health page and the capacity check: one place to ask whether Apelora is working.
• AlertsThe fifteen built-in alert rules, how they are evaluated, and how webhooks are signed.
• Moving modules and surviving failuresMoving modules between servers and surviving failures, with the measured timings.
• Restarting a virtual machineA virtual machine on shared storage starts again on another server after its server is fenced.
• Enrolling a serverHow a new server is approved, joined, and admitted.
• Installing a server with MAASHow Apelora uses MAAS to find, install, test, and power a machine.
• Sign-in methods: local accounts and a directoryLocal accounts and a directory beside identity providers: the design.
• Tenancy isolation and quotasEnvironments' Incus projects and quotas: design and evidence.
• Capacity: a global fabricAn order-of-magnitude estimate for a fabric of 50,000 servers and where the design must change.
• Studio architectureHow the Studio works: architecture of the designer.
• Studio interfaceThe Studio interface specification: layout, interactions, forms, motion and accessibility.