Skip to main content

Setup Commands

Test Connectivity

Check Orka Engine Version

Verify Python Version


One-Liner Examples

Install/Upgrade Orka Engine

Plan Deployment (Dry Run)

Deploy VM

Plan Deletion (Dry Run)

Delete VM

Stop VM

Start VM

Delete Single VM

List All VMs

List VMs by Name

Pull Image to All Hosts

Create and Push Custom Image

Create Image with OS Upgrade


Android Virtual Devices

Install Android SDK on Hosts

To force reinstallation on hosts where the SDK is already present:

Install SDK Platforms and System Images

With a specific platform and image types:

Create an AVD (Plan First)

Create an AVD

With custom platform, image type, and resources:

Manage AVD State

List AVDs

Delete AVD by Index

Uninstall SDK Platform


Common Variable Combinations

Deploy with Custom CPU and Memory

Deploy with Network Interface

Deploy to Specific Host

Image Creation with Auth

Insecure Registry


Image Naming Patterns

MacStadium Public Images

  • Tahoe: ghcr.io/macstadium/orka-images/tahoe:latest
  • Sequoia: ghcr.io/macstadium/orka-images/sequoia:latest
  • Sonoma: ghcr.io/macstadium/orka-images/sonoma:latest

Private Registry Format

  • Full path: registry.example.com/organization/repository:tag
  • With port: registry.example.com:5000/orka/image:v1.0

VM Naming Convention

VMs are identified individually by name. Use clear, descriptive names:
  • dev-desktop-01, dev-desktop-02
  • prod-build-runner, prod-build-runner-2
  • ci-macOS-sonoma
AVDs are named automatically based on the VM: {vm_name}-avd-0, {vm_name}-avd-1, etc.

Ansible Shortcuts

Run on Single Host

Dry Run (Check Mode)

Verbose Output

Run Specific Tags

Skip Tags

Step Through Tasks


Best Practices Checklist

Planning and Safety

  • Always use --tags plan before production deployments
  • Test playbooks on single host first with --limit
  • Review deployment plan output before executing
  • Verify capacity before large deployments

Naming and Organization

  • Use clear, descriptive VM names (for example, prod-desktop-01, build-runner-sonoma)
  • Version your images with tags (:v1.0, :v2.0, not :latest in prod)
  • Document VM purposes in inventory comments

Capacity Management

  • Set appropriate max_vms_per_host limits
  • Monitor disk space on hosts regularly
  • Keep Orka Engine updated across all hosts
  • Track VM distribution across hosts

Image Management

  • Place custom configuration scripts in /scripts directory
  • Test image builds in dev before production
  • Keep base images cached on all hosts
  • Implement regular image rebuild schedule

Security and Operations

  • Store credentials securely (Ansible Vault)
  • Maintain inventory file accuracy
  • Use SSH keys (not passwords) for host access
  • Rotate credentials regularly
  • Review deployment logs for errors

State and Tracking

  • Let Ansible manage VMs (use playbooks, not manual creation)
  • Use list.yml to verify state before changes
  • Keep group vars consistent across environments

Support Resources

  • Documentation: MacStadium
  • Support Portal: support@macstadium.com
  • CLI Reference: orka-engine --help
  • VM Commands: orka-engine vm --help
  • Image Commands: orka-engine image --help
  • Project README: Check your repository’s README.md for architecture details