cjsteel.bootstrap
Bootstrap
TESTING FORK - DO NOT USE - SEE ORIGINAL AUTHORS PAGE FOR ORIGINAL ROLE
This is a tool to set up your system so it can be managed by Ansible.
Example Playbook
Here's a simple example from molecule/resources/playbook.yml
:
---
- name: Converge
hosts: all
become: yes
gather_facts: no
roles:
- cjsteel.bootstrap
tasks:
- name: test connection
ping:
The machine you are using may not need any special setup.
No preparation required.
You can also see a complete explanation and example for using these roles.
Role Variables
These settings can be found in defaults/main.yml
:
---
# defaults file for bootstrap
# User to connect to machines.
bootstrap_user: root
# Software to support special modules (like mysql_db).
# Use "yes", "no" or leave it unset.
bootstrap_preview: yes
# Should the system wait for the host to be ready?
bootstrap_wait_for_host: no
# How many seconds to wait during a connection test before it fails.
bootstrap_timeout: 3
# How many retries during installation.
bootstrap_retries: 3
Requirements
- Access to a repository with packages, likely online.
- A recent version of Ansible. (Tests are performed on the current, previous, and next versions of Ansible.)
You can install the necessary roles using:
- none
Context
This role works with many other compatible roles. Check out the documentation of these roles for more information.
Compatibility
This role has been tested on the following systems and Ansible versions:
Distribution | Ansible 2.7 | Ansible 2.8 | Ansible devel |
---|---|---|---|
alpine-edge* | yes | yes | yes* |
alpine-latest | yes | yes | yes* |
archlinux | yes | yes | yes* |
centos-6 | yes | yes | yes* |
centos-latest | yes | yes | yes* |
debian-stable | yes | yes | yes* |
debian-unstable* | yes | yes | yes* |
fedora-latest | yes | yes | yes* |
fedora-rawhide* | yes | yes | yes* |
gentoo | yes | yes | yes* |
kali | yes | yes | yes* |
opensuse-leap | yes | yes | yes* |
ubuntu-devel* | yes | yes | yes* |
ubuntu-latest | yes | yes | yes* |
ubuntu-rolling | yes | yes | yes* |
(An asterisk means the build might not work, as it is experimental.)
Testing
Unit tests are run with every change and regularly.
If you encounter issues, please report them on GitHub.
To test this tool locally, use Molecule:
pip install molecule
molecule test
To test on Amazon EC2, set up ~/.aws/credentials and choose a region with export AWS_REGION=eu-central-1
before running molecule test --scenario-name ec2
.
There are many available scenarios; you can find them in the molecule/
folder.
License
Apache-2.0
Author Information
Prepare your system to be managed by Ansible.
ansible-galaxy install cjsteel.bootstrap