Your Ansible playbooks, run by a fast engine written in Rust.

Volant reads the playbooks, roles and inventories you already have and runs them over SSH. Nothing to convert.

curl -fsSL https://volant.sh/install.sh | sh

Linux and macOS, x86_64 and arm64. Ansible is not needed. Windows is not supported yet.

pre-alpha It runs real playbooks, not every playbook yet. Try it on a host you can afford to touch, and see what it leaves on your machines.

One run, five hosts.

A real run of Volant, replayed. Each spoke of the wheel stands for a host and takes the colour of the result it returns, in the colours ansible-playbook uses.

  • web1waiting
  • web2waiting
  • web3waiting
  • db1waiting
  • db2waiting

volant playbook -i inventory.ini site.yml

PLAY [all] *********************************************************************

TASK [Check the host answers] **************************************************
ok: [web1]
ok: [web2]
ok: [web3]
ok: [db1]
ok: [db2]

TASK [Write the app config] ****************************************************
changed: [web1]
changed: [web2]
changed: [web3]
changed: [db1]
changed: [db2]

TASK [Reload the web server] ***************************************************
changed: [web1]
changed: [web2]
changed: [web3]
skipping: [db1]
skipping: [db2]

TASK [Check the database port] *************************************************
skipping: [web1]
skipping: [web2]
skipping: [web3]
ok: [db1]
ok: [db2]

PLAY RECAP *********************************************************************
db1                        : ok=3    changed=1    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
db2                        : ok=3    changed=1    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
web1                       : ok=3    changed=2    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
web2                       : ok=3    changed=2    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
web3                       : ok=3    changed=2    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
The playbook and inventory of this run
- hosts: all
  gather_facts: false
  tasks:
    - name: Check the host answers
      ping:

    - name: Write the app config
      copy:
        dest: "/tmp/volant-demo/out/{{ inventory_hostname }}.conf"
        content: "role={{ group_names | first }}\n"

    - name: Reload the web server
      command: "true"
      when: "\"web\" in group_names"

    - name: Check the database port
      command: "true"
      changed_when: false
      when: "\"db\" in group_names"
[web]
web1
web2
web3

[db]
db1
db2

[all:vars]
ansible_connection=local
ansible_python_interpreter=/usr/bin/python3

Recorded with Volant 0.1.0-alpha.10 on five hosts over a local connection, and replayed here at reading speed. The output is what it printed.

How it works.

ansible-playbook pays for a new Python interpreter on the host for every task. Volant pays once per run, and keeps one connection open for the rest.

ansible-playbook for every task, on every host

  1. build the module payload
  2. send it over SSH
  3. start Python
  4. import module_utils
  5. run the module

Volant once per run

  1. upload a small agent, cached on the host
  2. open one SSH connection per host

then for every task

  1. send the task over the open link
  2. answer it in Rust, or fork a warm Python

Common modules such as apt, systemd, file, lineinfile and fact gathering are answered in Rust by the agent when a task’s arguments allow it. Every other module runs in Python, in a server that loaded its imports once. How the engine is built

Same files, same command.

volant playbook takes the options of ansible-playbook and prints the output you know, down to the recap. Everything your project already has is read as it is.

Run your first playbook

ansible.cfg
read from the same places, with the same precedence
Inventories
INI, YAML, TOML, scripts and inventory plugins
group_vars and host_vars
layered in Ansible’s order
Vault
vaulted files and values, --ask-vault-pass and --vault-id
Roles and collections
dependencies, argument specs and installed collections
Command line
the options of ansible-playbook, including --check and --diff

It says no before it touches a host.

Volant checks the whole playbook before it connects. Most of what this release cannot run is named there, with the play or task it is in, and the run stops with code 4. Nothing has changed on any host.

--syntax-check and the listings never stop on what is not supported, and --check with --diff shows what a real run would change. Check a project

$ volant playbook -i inventory.ini site.yml 
ERROR! play 1: strategy 'mitogen_free' is not supported yet
Real output of Volant 0.1.0-alpha.10, for a play that asks for a strategy this release does not have.
What it fetches
its own Python and ansible-core, about 155 MB, the first time a playbook needs Python
How it checks it
every file against a hash pinned in the release
Where it keeps it
~/.local/share/volant/runtime, apart from any system Python
Collections
volant runtime install --collections community.general
Without a network
volant runtime pack on one machine, install --from on the other

No Ansible to install.

The binary carries the agents it uploads to your hosts. When a playbook needs a Python module, Volant installs a runtime of its own and keeps it apart from the rest of the machine.

The managed runtime

What Volant promises.

Your files stay yours

No conversion step and no new format. The same files keep working with ansible-playbook.

Refusals come first

Most of what this release cannot run is named before the first connection, and nothing runs.

Linux over SSH first

Linux hosts over SSH and local connections today. Windows and network devices come later.

No telemetry

Volant makes no network call other than the ones your playbook asks for, and the runtime download.

Built in the open.

Volant is GPL-3.0-or-later, like Ansible. The roadmap, the issues and the decisions behind the design are public.