[Openstack] Cross-zone instance identifiers in EC2 API - Is it worth the effort?

Jay Pipes jaypipes at gmail.com
Fri Jul 8 13:58:38 UTC 2011


On Fri, Jul 8, 2011 at 9:54 AM, Soren Hansen <soren at linux2go.dk> wrote:
> 2011/7/8 Ed Leafe <ed.leafe at rackspace.com>:
>>        No, it would work more like: a new instance is requested, and the host selected. A candidate UUID would be generated and checked for "first 8" uniqueness (I had already added a db method to locate by the first 8 chars of a UUID across nested zones). When an acceptable UUID was generated, it would be passed to the selected host along with the create request. The instance would only have to be created once.
>
> If we're doing collision checking anyway, using UUID's to being with
> is pointless. We're effectively reduced to a 32 bit key space and,
> even worse, we're not being smart enough about it to actually do
> without the extra DB roundtrip to check for collisions.

That may be true, but only for the EC2 API, not the OpenStack API,
right? The question remains from my original post: do we really care
enough about this?

Put another way: do we want to expend more resources on an API we don't control?

-jay




More information about the Openstack mailing list