← Back to team overview

openstack team mailing list archive

Re: Instance IDs and Multiple Zones


Totally agree with Eric.

Two questions that I think can help us move forward:

   1. Is the decision to stick with integers still valid?  Can someone that
   was there give us the reason for the decision?  Is it documented anywhere?
   2. If "we must have integers" means that we get 128 bit 'random'
   integers, do we still want integers?


On Tue, Mar 22, 2011 at 11:25 AM, Eric Day <eday@xxxxxxxxxxxx> wrote:

> On Tue, Mar 22, 2011 at 12:40:21PM -0400, Ed Leafe wrote:
> >       The two obvious solutions are a) a single, shared database and b)
> using a UUID instead of an integer for the ID. Both of these approaches have
> been discussed and rejected, so let's not bring them back up now.
> We shouldn't dismiss previous ideas just because we've not chosen
> them in the past, but lets not have the same discussion.
> >       Given integer IDs and separate databases, the only obvious choice
> is partitioning the numeric space so that each zone starts its
> auto-incrementing at a different point, with enough room between starting
> ranges to ensure that they would never overlap. This would require some
> assumptions be made about the maximum number of instances that would ever be
> created in a single zone in order to determine how much numeric space that
> zone would need. I'm looking to get some feedback on what would seem to be
> reasonable guesses to these partition sizes.
> I think we need:
> * No central authority such as a globally shared DB. This also
>  means not partitioning some set and handing them out to zones as
>  offset (this is just another form of a shared DB).
> * Ability to seamlessly join existing zones without chance of namespace
>  collisions for peering and bursting. This means a globally unique
>  zone naming scheme, and for this I'll reiterate the idea of using
>  DNS names for zones.
> If we want to stick with a single DB per zone, as it looks like we
> are, this can simply be the auto-increment value from the instance
> table and the zone as: <instance>.<zone>.
> >       The other concern is more aesthetic than technical: we can make the
> numeric spaces big enough to avoid overlap, but then we'll have very large
> ID values; e.g., 10 or more digits for an instance. Computers won't care,
> but people might, so I thought I'd at least bring up this potential
> objection.
> I'm not concerned with aesthetic issues to be honest. We have
> copy/paste, DNS, and various techniques for presentation layers.
> -Eric
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp