ansible

ansible basic installation/configuration

jordi prats

eyp

4,194 downloads

4,194 latest version

5.0 quality score

Version information

  • 0.1.0 (latest)
released Aug 21st 2018
This version is compatible with:
  • Puppet Enterprise 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 3.8.0
  • RedHat
    ,
    CentOS
    ,
    Scientific
    ,
    OEL
    ,
    OracleLinux

Start using this module

Documentation

eyp/ansible — version 0.1.0 Aug 21st 2018

ansible

Table of Contents

  1. Overview
  2. Module Description
  3. Setup
  4. Reference
  5. Limitations
  6. Development

Overview

ansible basic installation/configuration

Module Description

This module ins intended to automate ansible's installation and basic setup

Setup

What ansible affects

  • Uses eyp-epel to install and enable EPEL
  • Installs via packaging system ansible
  • Manages ansible's general configuration file: /etc/ansible/ansible.cfg

Setup Requirements

This module requires pluginsync enabled

Beginning with ansible

Include ansible class to install it:

class { 'ansible': }

Reference

ansible

  • manage_package: Whether or not this module shall manage ansible's package (default: true)
  • package_ensure: Expected package status (default: 'installed')
  • roles_path: List of additional paths to search for roles in (default: [])
  • host_key_checking: SSH key host checking (default: false)
  • retry_files_enabled: Whether or not when a playbook fails a .retry file shall be created in ~/ (default: false)
  • log_path: Log file for ansible (default: '/var/log/ansible.log')
  • manage_logrotate: Whether or not to add logrotate config (default: true)
  • logrotation_ensure: Controls logrotate configutation files status (default: 'present')
  • logrotation_frequency: Logrotation frequency (default: 'daily')
  • logrotation_size: Max log size (default: '100M')
  • logrotation_rotate: Log retention (default: '30')

Limitations

RHEL 7 only

Development

We are pushing to have acceptance testing in place, so any new feature should have some test to check both presence and absence of any feature

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request