Jimmy McCrory 65b28f95bb Make all tests use upper-constraints
As per [1] all tests can now use upper-constraints. This patch removes
all instances of the install_command override relating to testing which
were needed to negate the use of upper-constraints.

[1] http://lists.openstack.org/pipermail/openstack-dev/2016-August/101474.html

Change-Id: I7b6051e9ea0c6e25901ff0fd24bbe5c011c38281
2017-02-09 18:21:39 -08:00
2016-09-07 15:36:45 +00:00
2016-09-20 14:07:27 -05:00
2015-10-14 21:23:11 -05:00
2016-09-07 15:36:45 +00:00
2016-09-06 10:24:58 -05:00
2016-09-07 15:36:45 +00:00
2016-06-13 13:37:04 +00:00
2016-05-04 14:13:33 +00:00
2016-04-02 14:46:00 -04:00
2016-05-03 21:00:42 +00:00
2016-07-08 17:14:04 +01:00
2017-02-09 18:21:39 -08: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
RETIRED, Security Role for OpenStack-Ansible
Readme 8.4 MiB