3ab781de65
Initially the intent for adding this was to better test any patches for roles together before they merge, but it has had the unintended side-effect of causing patches to take much longer to merge (because they all get lined up in a single queue, rather than independent queues) and a lot more infra resources are used (because a patch that fails at the top of the queue will result in all subsequent patches restarting all their tests). As discussed in the channel, we'd prefer to revert back to the previous independent queue method of testing. It has served us well. Change-Id: If45fbcaae3f0bd467c2d569e3b0dca14d373e108
ansible-hardening
The ansible-hardening role applies security hardening configurations from the Security Technical Implementation Guide (STIG) to systems running the following distributions:
- CentOS 7
- Debian Jessie
- Fedora 26
- openSUSE Leap 42.2 and 42.3
- Red Hat Enterprise Linux 7
- SUSE Linux Enterprise 12 (experimental)
- Ubuntu 16.04
For more details, review the ansible-hardening documentation.
Requirements
This role can be used with or without OpenStack-Ansible. It requires Ansible 2.3 or later.
Role Variables
All of the variables for this role are in defaults/main.yml.
Dependencies
This role has no dependencies.
Example Playbook
Using the role is fairly straightforward:
- hosts: servers
roles:
- ansible-hardening
Running with Vagrant
This role can be tested easily on multiple platforms using Vagrant.
The Vagrantfile supports testing on:
- Ubuntu 16.04
- CentOS 7
To test on all platforms:
vagrant destroy --force && vagrant up
To test on Ubuntu 14.04 only:
vagrant destroy ubuntu1404 --force && vagrant up ubuntu1404
To test on Ubuntu 16.04 only:
vagrant destroy ubuntu1604 --force && vagrant up ubuntu1604
To test on CentOS 7 only:
vagrant destroy centos7 --force && vagrant up centos7
License
Apache 2.0
Author Information
For more information, join #openstack-ansible on Freenode.