Go to file

Jesse Pretorius caa9733788 Keystone SSL cert/key distribution and configuration

This patch adds the option to provide an SSL certificate for the
Keystone service (either self-signed or user provided) and to
configure the endpoints and Keystone service appropriately.

* A new boolean variable called 'keystone_ssl' enables/disables
  the configuration of SSL for the Keystone service.

* The server key/certificate (and optionally a CA cert) are
  distributed to all keystone containers and used for the setup
  of SSL endpoints if the appropriate protocol is set.

* The internal/public and the admin endpoints can be set to be
  served via http or https seperately via the
  'keystone_service_*_proto' variables.

* The logic to determine the appropriate load balancing
  configuration based on the Keystone endpoint protocol has
  been implemented in the haproxy vars.

* Two new variables have been implemented for a user-provided
  server key and certificate:
  - keystone_user_ssl_cert: <path to cert on deployment host>
  - keystone_user_ssl_key: <path to cert on deployment host>
  If either of these is not defined, but a Keystone endpoint
  has been configured for SSL, then the missing cert/key
  will be self generated on the first Keystone container and
  distributed to the other containers.

* A new variable has been implemented for a user-provided CA
  certificate:
  - keystone_user_ssl_ca_cert: <path to cert on deployment host>

* A new variable called 'keystone_ssl_self_signed_subject' has
  been implemented to allow the user to override the certificate
  properties, such as the CN and subjectAltName.

Upgrade notes:

* The SSL-based client authentication configuration in Apache
  has been removed as it appears to be unused.

* The minimum Ansible version for the os_keystone and
  haproxy_server roles have been increased to v1.9.0 as it's
  the minimum version that supports ternary filters.

* The boolean 'keystone_ssl_enabled' has been renamed to
  'keystone_ssl'. This maintains a pattern set in the haproxy
  role for enablement of ssl offloading in the load balancer.

* The Apache configuration appropriately implements the
  'SSLCACertificateFile' instead of the 'SSLCACertificatePath'
  directive in order to ensure that the appropriate signing
  certificate is provided to the browser.

* The 'keystone_self_signed_regen' variable has been renamed
  to 'keystone_ssl_self_signed_regen'.

* The default names for the deployed keys/certificates have been
  changed:
  - /etc/ssl/certs/apache.cert  > /etc/ssl/certs/keystone.pem
  - /etc/ssl/private/apache.key > /etc/ssl/private/keystone.key

DocImpact
Partial-Bug: #1466827
Implements: blueprint keystone-federation
Change-Id: I4c5ea7b6bfc3d7d7230a7440fa501241826c9dee
Co-Authored-By: Miguel Grinberg <miguelgrinberg50@gmail.com>
(cherry picked from commit 4b35b3e929)

2015-08-20 17:03:39 +00:00

doc

Move developer documentation to its own subtree

2015-08-20 14:35:53 +00:00

etc

Add swift-sync role and environment

2015-08-07 16:16:21 -07:00

playbooks

Keystone SSL cert/key distribution and configuration

2015-08-20 17:03:39 +00:00

rpc_deployment

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

scripts

Enable debug logging for gate checks

2015-08-17 16:03:47 +00:00

.gitignore

Uses tox for automating documentation builds

2015-08-13 07:50:42 +01:00

.gitreview

Set gerrit default branch to kilo

2015-04-24 16:49:48 +00:00

ansible-role-requirements.yml.example

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

CONTRIBUTING.rst

Updating CONTRIBUTING for commit messages

2015-04-06 10:38:40 -05:00

dev-requirements.txt

Adds a pep8 target to tox.ini

2015-08-18 06:03:00 +00:00

development-stack.rst

fix bash/curl command in development-stack.rst

2015-05-27 17:23:47 +00:00

LICENSE.txt

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

README.rst

Small readme fix

2015-08-13 10:58:48 +00:00

requirements.txt

Remove python-openstacksdk version spec

2015-08-18 16:37:58 +01:00

setup.cfg

Uses tox for automating documentation builds

2015-08-13 07:50:42 +01:00

setup.py

Uses tox for automating documentation builds

2015-08-13 07:50:42 +01:00

tox.ini

Adds a pep8 target to tox.ini

2015-08-18 06:03:00 +00:00

README.rst

OpenStack Ansible Deployment

date: 2015-02-02 22:00
tags: lxc, openstack, cloud, ansible
category: *nix

Playbooks

There are several playbooks within that will setup hosts for use in OpenStack Cloud. The playbooks will enable LXC on hosts and provides the ability to deploy LXC containers for use within openstack.

Plays:

setup-hosts.yml Performs host setup for use with LXC in the OpenStack hosts.
setup-infrastructure.yml Performs all of the setup for all infrastructure components.
setup-openstack.yml Performs all of the setup for all of the OpenStack components.

If you dont want to run plays individually you can simply run setup-everything.yml which will perform all of the setup and installation for you.

Basic Setup:

If you have any roles that you'd like to have pulled in that are outside the scope and or replace modules within this repository please add them to the ansible-role-requirements.yml file. In this file you will want to fill in the details for the role you want to pull in using standard ansible galaxy format.

- name: SuperAwesomeModule
  src: https://github.com/super-user/SuperAwesomeModule
  version: master

Run the ./scripts/bootstrap-ansible.sh script, which will install, pip, ansible 1.9.x, all of the required python packages, and bring in any third party ansible roles that you may want to add to the deployment.
Copy the etc/openstack_deploy directory to /etc/openstack_deploy.
Fill in your openstack_deploy/openstack_user_config.yml, openstack_deploy/user_secrets.yml and openstack_deploy/user_variables.yml files which you've just copied to your /etc/ directory.
Generate all of your random passwords executing scripts/pw-token-gen.py --file /etc/openstack_deploy/user_secrets.yml.
Accomplish all of the host networking that you want to use within the deployment. See the etc/network directory in this repository for an example network setup.
When ready change to the playbooks/ directory and execute your desired plays. IE:

openstack-ansible setup-everything.yml

Notes

If you run the ./scripts/bootstrap-ansible.sh script a wrapper script will be added to your system that wraps the ansible-playbook command to simplify the arguments required to run openstack ansible plays. The name of the wrapper script is openstack-ansible.
The lxc network is created within the lxcbr0 interface. This supports both NAT networks as well as more traditional networking. If NAT is enabled (default) the IPtables rules will be created along with the interface as a post-up processes. If you ever need to recreate the rules and or restart the dnsmask process you can bounce the interface IE: ifdown lxcb0; ifup lxcbr0 or you can use the lxc-system-manage command.
The tool lxc-system-manage is available on all lxc hosts and can assist in recreating parts of the LXC system whenever its needed.
Inventory is generated by executing the playbooks/inventory/dynamic_inventory.py script. This is configured in the playbooks/ansible.cfg file.
If you don't use the pw-token-gen.py script you will want to ensure the permissions on /etc/openstack_deploy/user_secrets.yml are more secure. chmod 0600 /etc/openstack_deploy/user_secrets.yml

Bugs and Blueprints

Everything we do is in launchpad and gerrit. If you'd like to raise a bug, feature request, or are looking for ways to contribute please go to "https://launchpad.net/openstack-ansible".

Documentation

To build the docs make sure that you have installed the python requirements as found within the dev-requirements.txt file and then run the following command from within the doc directory.

make html