Open Stack

Without fixing the integer ID problem, I'd vote for reserving some bits for zone ID.  I don't like the idea assigning ranges to zones.  But I think the right answer is to fix the integer ID problem. 

On Mar 22, 2011, at 11:28 AM, Ed Leafe wrote:

> On Mar 22, 2011, at 1:45 PM, Jon Slenk wrote:
> 
>> if the schema cannot be changed (which might be worth reconsidering
>> since it seems to be a bit of a root cause of trouble) then maybe you
>> have to reserve the last 4 or 5 digits of the id to be the zone id,
>> and then autoincrement on top of that? on the assumption that there
>> would be a limit of 9999 or 99999 zones ever.
> 
> 	Just to be clear: I would not have been in favor of using integer IDs. However, this was discussed and settled before I was actively involved in the OpenStack code, so I didn't want to have this devolve into a resurrection of what had already been decided. If someone wants to restart that discussion, I'd certainly be interested, but that's not what I'm looking for in this thread.
> 
> 	The question before us is: given integer IDs, what is the best way to handle the added complexity of multiple zones?
> 
> 
> -- Ed Leafe
> 
> 
> 
> Confidentiality Notice: This e-mail message (including any attached or
> embedded documents) is intended for the exclusive and confidential use of the
> individual or entity to which this message is addressed, and unless otherwise
> expressly indicated, is confidential and privileged information of Rackspace.
> Any dissemination, distribution or copying of the enclosed material is prohibited.
> If you receive this transmission in error, please notify us immediately by e-mail
> at abuse at rackspace.com, and delete the original message.
> Your cooperation is appreciated.
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp