Open Stack

It was my plan to have the OpenStack name be CloudKeep. It's not Rackspace specific, so we can use it if we like it. We could also use just the name of the API project which would be Barbican. Either would be okay with me.


Jarret

From: Dolph Mathews <dolph.mathews at gmail.com<mailto:dolph.mathews at gmail.com>>
Reply-To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Wednesday, April 24, 2013 12:36 PM
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] Key Manager blueprint updated

I was under the impression that "CloudKeep" was a rackspace trademark, like "Cloud FIles" is for swift?


-Dolph


On Wed, Apr 24, 2013 at 12:29 PM, Mac Innes, Kiall <kiall at hp.com<mailto:kiall at hp.com>> wrote:
What about "CloudKeep"?

(Hint: I don't see anything on the wiki page explaining why RackSpace's
existing implementation can't be used as a starting point!)

Kiall Mac Innes
HP Cloud Services - DNSaaS

Mobile:   +353 86 345 9333<tel:%2B353%2086%20345%209333>
Landline: +353 1 524 2177<tel:%2B353%201%20524%202177>
GPG:      E9498407

On 24/04/13 18:07, Atwood, Mark wrote:
> Clipper?
>
> Mark Atwood <mark.atwood at hp.com<mailto:mark.atwood at hp.com> <mailto:mark.atwood at hp.com<mailto:mark.atwood at hp.com>>>
> Director of Open Source Evangelism for HP Cloud Services
> +1-206-473-7118<tel:%2B1-206-473-7118>
>
>
> On Tue, Apr 23, 2013 at 1:09 AM, Bhandaru, Malini K
> <malini.k.bhandaru at intel.com<mailto:malini.k.bhandaru at intel.com> <mailto: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.____
>
>     __ __
>
>     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<mailto:OpenStack-dev at lists.openstack.org>
>     <mailto:OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto: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/20130424/75e00e66/attachment.html>