- follow the standard installation pattern for barbicanclient: only clones if it is installed from source. This way it is possible to install and test barbicanclient from pip by default, additional jobs can simply add it to required-projects; - define the repository metadata using the GIT* arrays. They are also defined by stackrc, but they should be probably removed from there; - remove the useless call of configure_barbicanclient (the same steps are already performed by install_barbicanclient). Going forward, configure_barbicanclient can be removed Change-Id: Iea1cd3f82c3b38f03f91b0191846e1ddbbfb1d6c (cherry picked from commit
|5 months ago|
|api-guide/source||1 year ago|
|api-ref/source||2 years ago|
|barbican||7 months ago|
|bin||1 year ago|
|devstack||3 months ago|
|doc||1 year ago|
|etc||2 years ago|
|functionaltests||8 months ago|
|playbooks/legacy||11 months ago|
|releasenotes||1 year ago|
|.coveragerc||3 years ago|
|.gitignore||1 year ago|
|.gitreview||11 months ago|
|.mailmap||6 years ago|
|.stestr.conf||1 year ago|
|.zuul.yaml||4 months ago|
|HACKING.rst||1 year ago|
|LICENSE||7 years ago|
|README.md||1 year ago|
|apiary.apib||3 years ago|
|babel.cfg||7 years ago|
|bindep.txt||2 years ago|
|lower-constraints.txt||1 year ago|
|requirements.txt||1 year ago|
|setup.cfg||1 year ago|
|setup.py||3 years ago|
|test-requirements.txt||1 year ago|
|tox.ini||8 months ago|
Barbican is a REST API designed for the secure storage, provisioning and management of secrets. It is aimed at being useful for all environments, including large ephemeral Clouds.
The full documentation can be found on the Barbican Developer Documentation Site.
If you have a technical question, you can ask it at Ask OpenStack with the
barbican tag, or you can
send an email to the OpenStack General mailing list at
firstname.lastname@example.org with the prefix
[barbican] in the
To file a bug, use our bug tracker on OpenStack Storyboard.
Release notes for the project can be found at( https://docs.openstack.org/releasenotes/barbican).
For development questions or discussion, hop on the OpenStack-dev mailing list
email@example.com and let us know what you think, just add
[barbican] to the subject. You can also join our IRC channel
#openstack-barbican on Freenode.
Barbican began as part of a set of applications that make up the CloudKeep ecosystem. The other systems are:
Please visit our Users, Developers and Operators documentation for details.
The current state of key management is atrocious. While Windows does have some decent options through the use of the Data Protection API (DPAPI) and Active Directory, Linux lacks a cohesive story around how to manage keys for application use.
Barbican was designed to solve this problem. The system was motivated by internal Rackspace needs, requirements from OpenStack and a realization that the current state of the art could use some help.
Barbican will handle many types of secrets, including:
For the symmetric and asymmetric key types, Barbican supports full life cycle management including provisioning, expiration, reporting, etc. A plugin system allows for multiple certificate authority support (including public and private CAs).