Go to file

Panagiotis Karalis dc536599f8 Tacker uses OpenStack Barbican for secret keys

Use the OpenStack Barbican component instead of OpenStack Keystone
as secret key handler.
The reason behind is the way that Tacker handles the secret keys of
complex scenarios (specially the scenarios with HA) and how they are
stored or retrieved between different VMs or Blades.

Change-Id: I63d40c5239d2585e8bb7ac3b9338252c9e28c4c6
Signed-off-by: Panagiotis Karalis <pkaralis@intracom-telecom.com>

2018-10-05 10:37:51 +03:00

defaults

Tacker uses OpenStack Barbican for secret keys

2018-10-05 10:37:51 +03:00

doc

Follow the new PTI for document build

2018-07-13 16:00:06 +01:00

files/rootwrap.d

Update paste, policy and rootwrap configurations 2017-12-19

2017-12-20 18:48:29 +00:00

handlers

Clean up the remaining stuff for dashboard

2018-10-04 14:36:25 +08:00

README.rst

Tacker role for OpenStack-Ansible

Ansible role to install OpenStack Tacker.

Documentation for the project can be found at:: https://docs.openstack.org/openstack-ansible-os_tacker/latest/
Release notes for the project can be found at:: https://docs.openstack.org/releasenotes/openstack-ansible-os_tacker
The project source code repository is located at:: https://git.openstack.org/cgit/openstack/openstack-ansible-os_tacker
The project home is at:: https://launchpad.net/openstack-ansible