openstack team mailing list archive

Thread
Date

Re: Cross-zone instance identifiers in EC2 API - Is it worth the effort?

To: Thorsten von Eicken <tve@xxxxxxxxxxxxxx>, Soren Hansen <soren@xxxxxxxxxxx>
From: Ewan Mellor <Ewan.Mellor@xxxxxxxxxxxxx>
Date: Fri, 8 Jul 2011 01:49:59 +0100
Accept-language: en-US
Acceptlanguage: en-US
Cc: "openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx>
In-reply-to: <4E15CB2C.4090501@rightscale.com>
Thread-index: Acw8vAiDqRDlTlkBQT6Sra9BnXj6dwAQ0xBA
Thread-topic: [Openstack] Cross-zone instance identifiers in EC2 API - Is it worth the effort?

> From Thorsten von Eicken
> 
> FYI, there's nothing in the EC2 API that limits instance identifiers
> (or other IDs) to 32 bits. The IDs are strings, so it's trivial for EC2 to
> add another digit when running out of 32-bit IDs.

If that's the case (and I believe you, that's always how I assumed it would be) why don't we just make the EC2 ID be ami-<uuid>?

Ewan.

Follow ups

Re: Cross-zone instance identifiers in EC2 API - Is it worth the effort?
From: Soren Hansen, 2011-07-08

References

Cross-zone instance identifiers in EC2 API - Is it worth the effort?
From: Jay Pipes, 2011-07-06
Re: Cross-zone instance identifiers in EC2 API - Is it worth the effort?
From: Soren Hansen, 2011-07-07
Re: Cross-zone instance identifiers in EC2 API - Is it worth the effort?
From: Thorsten von Eicken, 2011-07-07