[openstack-dev] Key Manager blueprint updated

Bhandaru, Malini K malini.k.bhandaru at intel.com
Tue Apr 23 18:16:47 UTC 2013

Smiles - Ignite/Ignition  .. it certainly will ignite all the OpenStack encryption efforts

1. to catch fire or set fire to; burn or cause to burn
2. (Chemistry) (tr) Chem to heat strongly
3. (tr) to stimulate or provoke the case has ignited a nationwide debate


From: Dolph Mathews [mailto:dolph.mathews at gmail.com]
Sent: Tuesday, April 23, 2013 6:34 AM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] Key Manager blueprint updated



On Tue, Apr 23, 2013 at 3:09 AM, Bhandaru, Malini K <malini.k.bhandaru at intel.com<mailto:malini.k.bhandaru at intel.com>> wrote:
Hello Everyone!

Thank you to those of you who attended the key manager design summit session and provided input.
Missed some of you who have provided feedback on the mailing list.

I've updated the blueprint based on the discussions.  Do let me know if you are in favor of
Limiting access to keys based on original owner (user/project/tenant). With this approach, a put/create would need an additional
Argument to indicate scope.

I anticipate over this week breaking out the details into sub-blueprints for easier parceling into implementation sub-units.


Also open to suggestions for a name for the project :)

Jangle - the sound a bunch of keys  make?
Key Manager   (no obfuscation !)
(keystore is too similar to keystone ..  -1)


OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130423/4f0ba9a1/attachment.html>

More information about the OpenStack-dev mailing list