Files

Ian Cordasco ff2ed22c90 Add support for deploying Keystone with Fernet

This change adds a number of new tasks that are dependent on the value
of the Keystone token provider (keystone_token_provider) user variable.

If the keystone_token_provider user_variable is set to
keystone.token.providers.fernet.Provider then the playbooks will
appropriately create the fernet keys and distribute them to the rest of
the keystone containers.

This also implements key rotation for generated fernet keys similar to
how the os_nova roles implement key rotation.

Finally, we also need to build cryptography from master for now.
Currently, 0.8.x and 0.9.x use versions of cffi<1.0 which causes a bug
when used with mod_wsgi and Apache. This is fixed in cryptography master
and will be released in 1.0.

Closes-bug: 1463569
Change-Id: I8605e0490a8889d57c6b1b7e03e078fb0da978ab

2015-06-22 08:53:53 -05:00

openstack_clients.yml

Updated all of master to the latest SHAs

2015-06-08 17:18:14 -05:00

openstack_other.yml

Add support for deploying Keystone with Fernet

2015-06-22 08:53:53 -05:00

openstack_services.yml

Added flag to instruct yaprt to ignore tempest

2015-06-20 23:04:07 -05:00

python2_lxc.yml

Moved the playbook vars to defaults

2015-05-14 12:32:36 -05:00

readme.rst

Moved the playbook vars to defaults

2015-05-14 12:32:36 -05:00

readme.rst

Packages built by python from git

date: 2014-09-01 09:57
tags: python, pip, wheel, lxc, openstack, cloud, ansible
category: *nix

Packages Downloads and Installable

Any and all packages that need to be installed for this repository to work should be specified here in the, repo_packages directory. The files in this directory are given to the python wheel builder for construction.

Inside these files all download-able objects such as tar-balls and random files should also be specified. While the packaging roles may not be used to process these links the stated purpose of this directory is to have anything that is "installable" in a single location with the goal to allow for easily manipulation of requirements as they change.

NOTICE on items in this file:

If you use anything in the "*._git_install_branch" field that is not a TAG make sure to leave an in-line comment as to "why".

For the sake of anyone else editing this file:

If you add clients to this file please do so in alphabetical order.
Every entry should be name spaced with the name of the client followed by an "_"

The basic structure of all of these files:

git_repo: string URI to the git repository to clone from.
git_fallback_repo: string URI to an alternative git repository to clone from when git_repo fails.
git_dest: string full path to place a cloned git repository. This will normally incorporate the repo_path variable for consistency purposes.
git_install_branch: string branch, tag or SHA of a git repository to clone into.
git_repo_plugins: list of hashes with keys: path, package | This is used to install additional packages which may be installable from the same base repository.