Skip to Content

Ansible directly

Run the role on this machine or against your own inventory, from Rookery or without it.

Rookery's install methods are wrappers around one Ansible role, provision/ansible/roles/rookery in the provisioning source. It can also run on its own.

Dedicated machines only

Ansible does not partition anything, but the role installs services, changes the firewall policy and grants host-wide sudo. Run it only on a machine set aside for agents, not on your everyday computer.

From Rookery

This machine or an inventory on the Install tab runs the role with the host's profile. Ansible inventory and Ask for sudo password are on the Run tab. With the inventory blank it provisions the machine Rookery runs on, and the Run tab warns of that. With a path, it runs against the hosts in that inventory.

Without Rookery

Install Ansible into a virtualenv in a source checkout first, and point Ansible at the role's settings, as Rookery does:

python3 -m venv .venv && .venv/bin/pip install -r provision/requirements.txt
export ANSIBLE_CONFIG=provision/ansible.cfg

On the target itself:

.venv/bin/ansible-playbook -i localhost, -c local provision/ansible/site.yml \
  --become --ask-become-pass -e rookery_profile=cloud

Targets

rookery_profile selects defaults for the target, the kind of machine the host is installed on. A Rookery profile says it as target:

TargetFor
laptopPhysical machines, with the LightDM login and power defaults
cloudCloud instances, virtual machines and tests. Set a bootstrap SSH CIDR to limit SSH, such as 10.0.2.2/32 for a QEMU guest
containerThe container image

Cloud networking and disks are left as they are on every target. The agent's username and home are configurable, and its UID is discovered rather than assumed.

Settings

Every rookery_ setting has its default in provision/ansible/roles/rookery/defaults/main.yml. In a Rookery profile they go under ansible_vars; with plain Ansible, in the inventory or with -e. Plugins are chosen with rookery_plugin_features, and plugins outside the source's plugins/ folder are found through rookery_plugin_dirs ({"ID": "/path"}).

External programs are installed as the agent. Versions are pinned where upstream allows it. See Tools and Validation.

Edit on GitHub

Last updated on

On this page