Kevin Carter 427cd00acd Enable log collection after functional testing
This change enables log collection within the gate so that further analysis
on gate tasks can be performed post build. This is very useful when
debugging problems.

Change-Id: I41e70d0f6a0e5fed78e0a5462ee4d1730c94ec21
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
2016-08-29 21:38:38 -05:00
2016-08-26 09:17:18 -05:00
2016-08-25 20:54:41 +00:00
2016-08-26 15:43:13 -05:00
2016-08-22 16:09:31 -05:00
2015-10-05 17:37:21 +00:00
2016-08-22 21:29:21 +00:00
2016-07-15 11:26:50 +00: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

This role can be tested easily on multiple platforms using Vagrant.

The Vagrantfile supports testing on:

  • Ubuntu 14.04
  • 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.

Description
Ansible role for security hardening
Readme 5.4 MiB
Languages
Jinja 44.5%
Python 41.2%
Shell 14.3%