[install-guide] remove redundant part for security hardening
Currently, the contents for security hardening repeat on two pages in the install guide. Change-Id: I4c77f7a0c28564e56930ad9ffc3679b78566a978 closes-bug: #1624411
This commit is contained in:
parent
40ea97eef0
commit
3917510cf0
@ -48,47 +48,3 @@ this configuration, your ``openstack_user_config.yml`` would look like this:
|
||||
The configuration above deploys a memcached container and a database
|
||||
container on each host, without the RabbitMQ containers.
|
||||
|
||||
|
||||
.. _security_hardening:
|
||||
|
||||
Security hardening
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
OpenStack-Ansible automatically applies host security hardening configurations
|
||||
using the `openstack-ansible-security`_ role. The role uses a version of the
|
||||
`Security Technical Implementation Guide (STIG)`_ that has been adapted for
|
||||
Ubuntu 14.04 and OpenStack.
|
||||
|
||||
The role is applicable to physical hosts within an OpenStack-Ansible deployment
|
||||
that are operating as any type of node, infrastructure or compute. By
|
||||
default, the role is enabled. You can disable it by changing a variable
|
||||
within ``user_variables.yml``:
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
apply_security_hardening: false
|
||||
|
||||
When the variable is set to ``true``, the ``setup-hosts.yml`` playbook applies
|
||||
the role during deployments.
|
||||
|
||||
You can apply security configurations to an existing environment or audit
|
||||
an environment using a playbook supplied with OpenStack-Ansible:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
# Perform a quick audit using Ansible's check mode
|
||||
openstack-ansible --check security-hardening.yml
|
||||
|
||||
# Apply security hardening configurations
|
||||
openstack-ansible security-hardening.yml
|
||||
|
||||
For more details on the security configurations that will be applied, refer to
|
||||
the `openstack-ansible-security`_ documentation. Review the `Configuration`_
|
||||
section of the openstack-ansible-security documentation to find out how to
|
||||
fine-tune certain security configurations.
|
||||
|
||||
.. _openstack-ansible-security: http://docs.openstack.org/developer/openstack-ansible-security/
|
||||
.. _Security Technical Implementation Guide (STIG): https://en.wikipedia.org/wiki/Security_Technical_Implementation_Guide
|
||||
.. _Configuration: http://docs.openstack.org/developer/openstack-ansible-security/configuration.html
|
||||
.. _Appendix H: ../install-guide/app-custom-layouts.html
|
||||
|
||||
|
@ -25,7 +25,7 @@ Checking the integrity of your configuration files
|
||||
|
||||
Before running any playbook, check the integrity of your configuration files.
|
||||
|
||||
#. Ensure all files edited in ``/etc/`` are Ansible
|
||||
#. Ensure all files edited in ``/etc/openstack_deploy`` are Ansible
|
||||
YAML compliant. Guidelines can be found here:
|
||||
`<http://docs.ansible.com/ansible/YAMLSyntax.html>`_
|
||||
|
||||
@ -213,7 +213,7 @@ Verifying the Dashboard (horizon)
|
||||
|
||||
#. Authenticate using the username ``admin`` and password defined by the
|
||||
``keystone_auth_admin_password`` option in the
|
||||
``/etc/openstack_deploy/user_variables.yml`` file.
|
||||
``/etc/openstack_deploy/user_secrets.yml`` file.
|
||||
|
||||
.. TODO Add troubleshooting information to resolve common installation issues
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user