openstack team mailing list archive

[Sandy Walsh <sandy.walsh@xxxxxxxxxxxxx>]

Agreed. 

That's the downside of not having control of an API. Unless we do the "Embrace and Extend" thing, but that just seems fraught with problems if Amazon should zig when we zag. 

That said, top-level Zones may still operate using EC2 API, but all child-zones may be OS-API. We'd only need to translate at the outer level. Kind of like a Facade.

-S
________________________________________
From: openstack-bounces+sandy.walsh=rackspace.com@xxxxxxxxxxxxxxxxxxx [openstack-bounces+sandy.walsh=rackspace.com@xxxxxxxxxxxxxxxxxxx] on behalf of Jay Pipes [jaypipes@xxxxxxxxx]
Sent: Wednesday, July 06, 2011 8:35 PM
To: openstack@xxxxxxxxxxxxxxxxxxx
Subject: [Openstack] Cross-zone instance identifiers in EC2 API - Is it worth the effort?

Hey all,

Recently, Nova added support for multiple zones in the OpenStack API.
Using the nova-manage tool, you can get a list of instances in a
single zone or in multiple zones using the --recurse option. When just
querying a local zone's API server, the listed instance identifiers
will be integer IDs. When using the --recurse option, the listed
instance identifiers are UUIDs since they are globally unique.

Multiple zones is currently only supported in the OpenStack API, and
the question has been raised whether effort should be expended to get
parity in the EC2 API for this. The problem with the EC2 API is that
we do not have control over the instance identifiers -- they are an 8
character text string. We would still need to map the EC2 instance
identifier to some globally unique identifier (like a UUID), but the
solutions for how to do this aren't pretty (see
http://etherpad.openstack.org/EC2UUID).

Personally, I don't think it is worth expending the effort to get this
feature parity between the OpenStack API and the EC2 API, especially
considering we have little (or no) control over the EC2 API.

Thoughts?
-jay

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp
This email may include confidential information. If you received it in error, please delete it.