yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #36381
[Bug 885090] Re: EC2 and OS Image APIs use inconsistent IDs
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/885090
Title:
EC2 and OS Image APIs use inconsistent IDs
Status in ec2-api:
Invalid
Status in OpenStack Compute (nova):
Invalid
Bug description:
When retrieving images through the EC2 API, the image id looks like
"ami-00000001"; when using the OS API it looks like "1". Sadly the
EC2 API only accepts the "ami-00000001" format, which means that if
you query the OS API to get the image (which you have to do to get the
metadata) you then can't use that image API to create an instance
(which you have to do to specify an SSH key). While I can perform the
same mapping that the EC2 API no doubt does under the covers, I really
shouldn't have to - I suggest that the EC2 API should be returned in
the metadata, or the EC2 API create call should accept an OS Image Id.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ec2-api/+bug/885090/+subscriptions