[openstack-dev] [nova] keypair quota usage info for user

Jeremy Stanley fungi at yuggoth.org
Fri Jul 27 19:54:27 UTC 2018


On 2018-07-27 14:20:01 -0500 (-0500), Matt Riedemann wrote:
[...]
> Note the entries in there about how several deployments don't rely
> on nova's keypair interface because of its clunky nature, and
> other ideas about getting nova out of the keypair business
> altogether and instead let barbican manage that and nova just
> references a key resource in barbican. Before we'd consider making
> incremental changes to nova's keypair interface and user/project
> scoping, I think we would need to think through that barbican
> route and what it could look like and how it might benefit
> everyone.

If the Nova team is interested in taking it in that direction, I'll
gladly lobby to convert the "A Castellan-compatible key store" entry
at
https://governance.openstack.org/tc/reference/base-services.html#current-list-of-base-services
to a full on "Barbican" entry (similar to the "Keystone" entry). The
only thing previously standing in the way was a use case for a
fundamental feature from the trademark programs' interoperability
set.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180727/9b7e7173/attachment.sig>


More information about the OpenStack-dev mailing list