Re: [Openstack] Pondering multi-tenant needs in nova.

Strongly disagree, but nicely, of course :) I'll disagree by showing you an example of why not having a queryable org model is problematic: Let's say we go ahead and do what Glen suggests and have a string account ID that is then attached to the user in a one to many relationship. In SQL (MySQL

Re: [Openstack] Pondering multi-tenant needs in nova.

+1 !! - Chris On Feb 6, 2011, at 6:57 AM, Jay Pipes jaypi...@gmail.com wrote: Strongly disagree, but nicely, of course :) I'll disagree by showing you an example of why not having a queryable org model is problematic: Let's say we go ahead and do what Glen suggests and have a string

Re: [Openstack] Google Summer of Code 2011

You can count on me to participate as a student, looking forward to contribute to Openstack in GSoC ;-) . Ricky 2011/2/5 Eric Day e...@oddments.org: Having been a mentor before for other projects, I strongly agree that we should do this. It's a great way to get more folks involved in the

Re: [Openstack] Pondering multi-tenant needs in nova.

I disagree with your disagreement. :) When we have string based ID's like this, it doesn't need to translate directly into a varchar column for operations. First, auth data may not be stored as SQL at all for some systems and could be broken out into key/value pairs with some indexed. It could