96079d2280
Some OpenStack infra images don't have AppArmor enabled by default and this causes V-51337 to fail. This patch skips the task where AppArmor tag is checked. Closes-Bug: 1554654 Change-Id: Icf653e2b8f84dbaee76d77f99020879d2e5aa4ea |
||
---|---|---|
defaults | ||
doc | ||
files | ||
handlers | ||
meta | ||
tasks | ||
templates | ||
tests | ||
vars | ||
.gitignore | ||
.gitreview | ||
LICENSE | ||
README.md | ||
README.rst | ||
Vagrantfile | ||
other-requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.md
openstack-ansible-security
The goal of the openstack-ansible-security role is to improve security within openstack-ansible deployments. The role is based on the Security Technical Implementation Guide (STIG) for Red Hat Enterprise Linux 6.
Requirements
This role can be used with or without the openstack-ansible role. It requires Ansible 1.8.3 at a minimum.
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:
- openstack-ansible-security
Running with Vagrant
Security Ansible can be easily run for testing using Vagrant.
To do so run:
vagrant destroy
To destroy any previously created Vagrant setup
vagrant up
Spin up Ubuntu Trusty VM and run ansible-security against it
License
Apache 2.0
Author Information
For more information, join #openstack-ansible
on Freenode.