Glossary
| Term | Definition |
| Node | The Host Machine that will have Anka Virtualization installed and run VMs. |
| Template | What we call a VM after it has been tagged. See Tag. |
| Tag | VM Templates can have multiple Tags. The Tag is a label given to the specific state of the VM when it was saved. |
| OCI Tag | A tag in an OCI registry. An OCI tag is a full tag or a thin tag. A full tag includes the macOS disk. A thin tag holds only file layers, and you can pull it onto any VM. Thin tags stack on the VM in the order you pull them. The Anka Registry stores only full tags, and does not store thin tags. See OCI tags. |
| Ankafile | A file that lists the macOS version and the thin OCI Tags to pull, in order. |
| Registry | The Registry is a component of the Anka Build Cloud. It acts as a centralized storage and distribution system, containing Anka VM Templates + Tags. The Anka CLI can also use an OCI registry. See Templates and Registries. |
| Controller | The Controller is a component of the Anka Build Cloud. It provides a management UI, API, and task management layer for users and clients to manage Templates + Tags, Anka VMs, and the Nodes they run on. |
| Agent | Sometimes referred to as the “cloud agent” or “cluster agent”, this service runs on Anka Nodes and handles communication with the Controller. It is responsible for all host-level execution of Anka CLI commands. |
| Instance | The name given to a scheduled VM by the Controller. |