Remove PostgreSQL support
It was deprecated during the previous cycle[1], due to neutron which already removed PostgreSQL support.
[1] 0c4812f8815812a0e938089239f5a4964f8e37c4
Change-Id: I7bbfa84f75130fcf90e932ccf1a379e226eae244 Signed-off-by: Takashi Kajinami kajinamit@oss.nttdata.com
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
Team and repository tags
barbican
Table of Contents
Overview
The barbican module is a part of OpenStack, an effort by the OpenStack infrastructure team to provide continuous integration testing and code review for OpenStack and OpenStack community projects not part of the core software. The module itself is used to flexibly configure and manage the Key management service for OpenStack.
Module Description
The barbican module is a thorough attempt to make Puppet capable of managing the entirety of barbican. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the barbican module to assist in manipulation of configuration files.
Setup
What the barbican module affects
Installing barbican
barbican is not currently in Puppet Forge, but is anticipated to be added soon. Once that happens, you’ll be able to install barbican with:
Beginning with barbican
To utilize the barbican module’s functionality you will need to declare multiple resources. The following is a modified excerpt from the openstack module. This is not an exhaustive list of all the components needed, we recommend you consult and understand the openstack module and the core openstack documentation.
Implementation
barbican
barbican is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Limitations
Development
Developer documentation for the entire puppet-openstack project.
Release Notes
Contributors
Repository