[openstack-dev] Key Manager blueprint updated

Dolph Mathews dolph.mathews at gmail.com
Tue Apr 23 13:33:34 UTC 2013


ignition?


-Dolph


On Tue, Apr 23, 2013 at 3:09 AM, Bhandaru, Malini K <
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.****
>
> ** **
>
> https://wiki.openstack.org/wiki/KeyManager****
>
> ** **
>
> Also open to suggestions for a name for the project J****
>
> ** **
>
> Jangle – the sound a bunch of keys  make?****
>
> Key Manager   (no obfuscation !)****
>
> (keystore is too similar to keystone ..  -1)****
>
> ** **
>
> Regards****
>
> Malini****
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> 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/20130423/0ccf7c18/attachment.html>


More information about the OpenStack-dev mailing list