Reference
Targets
Where an Isoloom environment can run: Docker, hosted, Docker on a cloud VM, local VMs with Vagrant, Proxmox, one cloud VM per machine, and Ludus.
A target is a place an environment can run. Each needs one of the two implementations on every machine.
| Target | Runs as | Needs | Generator |
|---|---|---|---|
docker | Containers on the user's Docker | docker: | Available |
hosted | Containers run by a hosting service for the user | docker: | Planned |
cloud-docker | Docker on one cloud VM (AWS, Azure, GCP, DigitalOcean, Linode, Oracle) | docker: | Planned |
vagrant | One local VM per machine (VirtualBox, VMware, Parallels, libvirt) | vm: | Available |
proxmox | One VM per machine on a Proxmox server, with its own SDN network | vm: | Planned |
cloud-vm | One cloud VM per machine, subnets and security rules | vm: | Planned |
ludus | An export for teams that run Ludus | vm: | Planned |
isoloom targets lists the targets a spec can use and, for the others, which machines lack an
implementation.
Windows and other OS images
os: names one OS for every target; each target maps it to an image it can use:
- Local VMs and Proxmox: images built on the user's own machine or server from the vendor's installation media. Isoloom never redistributes Windows images.
- Cloud: the provider's own images. For Windows, AWS, Azure and Google Cloud offer license-included images billed by the hour, which makes the cloud the easiest place to run a Windows domain.
Cost and size
Every machine has resources: (or the defaults). isoloom resources adds them up, which is what
a laptop needs for local VMs, or what a cloud account will be billed per hour of running time.