Go to file
Major Hayden fa2800419e Migrate to unique variable names
This patch migrates all of the remaining non-unique variable names
in the security role to a pattern that begins with `security_*`.
This will reduce potential variable collisions with other roles.

This is a breaking change for deployers and users who are moving
from the liberty or stable/mitaka branches to master. Release notes
are included with additional details to help with the transition.

Closes-Bug: 1578326

Change-Id: Ib716e81e6fed971b21dc5579ae1a871736e21189
2016-05-09 16:18:48 -05:00
2016-05-09 16:18:48 -05:00
2016-05-09 16:18:48 -05:00
2016-05-09 16:18:48 -05:00
2016-05-09 16:18:48 -05:00
2016-05-09 16:18:48 -05:00
2016-05-04 08:56:41 -05:00
2015-10-05 17:37:21 +00:00
2015-10-09 08:25:56 -05:00
2016-05-03 08:58:41 +01:00

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.

Description
Ansible role for security hardening
Readme 5.6 MiB
Languages
Jinja 51.9%
Python 47.9%
Shell 0.2%