[openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?
Tim Bell
Tim.Bell at cern.ch
Tue Jan 17 10:42:44 UTC 2017
On 17 Jan 2017, at 11:28, Maish Saidel-Keesing <maishsk at maishsk.com<mailto:maishsk at maishsk.com>> wrote:
Please see inline.
On 17/01/17 9:36, Tim Bell wrote:
...
Are we really talking about Barbican or has the conversation drifted towards Big Tent concerns?
Perhaps we can flip this thread on it’s head and more positively discuss what can be done to improve Barbican, or ways that we can collaboratively address any issues. I’m almost wondering if some opinions about Barbican are even coming from its heavy users, or users who’ve placed much time into developing/improving Barbican? If not, let’s collectively change that.
When we started deploying Magnum, there was a pre-req for Barbican to store the container engine secrets. We were not so enthusiastic since there was no puppet configuration or RPM packaging. However, with a few upstream contributions, these are now all resolved.
the operator documentation has improved, HA deployment is working and the unified openstack client support is now available in the latest versions.
Tim - where exactly is this documentation?
We followed the doc for installation at http://docs.openstack.org/project-install-guide/newton/, specifically for our environment (RDO/CentOS) http://docs.openstack.org/project-install-guide/key-manager/newton/
Tim
These extra parts may not be a direct deliverable of the code contributions itself but they make a major difference on deployability which Barbican now satisfies. Big tent projects should aim to cover these areas also if they wish to thrive in the community.
Tim
Thanks,
Kevin
Brandon B. Jozsa
--
Best Regards,
Maish Saidel-Keesing
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170117/fb9ffecd/attachment.html>
More information about the OpenStack-dev
mailing list